Minor tweaks to issue-opening bot

[larsoner]

Leaving as draft for a few days in case there are other tweaks now that we have issues in the open. But from looking and using it:

1. Add job-level annotations (I was on a job page and saw nothing -- redundant with the action summary but puts in two places which helps discoverability)
2. Add 🤖 to last line of opened issue to make it visually clearer it's a bot-opened issue
3. Tweak dry-run wording (it says it opened the issue... but it would open the issue)
4. Adds note that the "last updated" on the Anaconda site is not the last uploaded wheel -- deleting an old wheel counts as an update (and so the "last updated" date reflects the deletion date, not the most-recent-upload date)

---

• Resolves Publish stale wheels report as a status page website  #181

[larsoner]

I'll take care of #181 here once we converge on how to publish the dates!

[larsoner]

@bsipocz locally doing:

$ export ISSUE_OPENER_TOKEN=$(gh auth token) GITHUB_TOKEN=$(gh auth token)
$ uv run --with-requirements tools/requirements.txt tools/check_stale_wheels.py --dry-run --html site/index.html
Acting as larsoner
$ open site/index.html

I see:

Ready for review/merge from my end!

[matthewfeickert]

At the moment the deployment is

$ tree ./site/
./site/
├── index.html
└── status.css

1 directory, 2 files

To avoid moving the page later if we want to use the top level for different information, can we have this either deploy to site/status.html with a landing page that routes there? If that's too much work to get something up today can we just copy index.html to status.html until we do something else so we know that status.html will work in the future?

[larsoner]

I'll see if I can get the README as the landing page with a pointer to the status page

[larsoner]

Okay now index.html:

With a pointer at the top to status.html:

[matthewfeickert]

Thanks @larsoner