Example created issue: #166.

One thing: this will create a new issue each time the staging tests fail, which could happen several times (on the cron schedule) before a fix is implemented and applied. I'm not sure if that's worth addressing now.

One thing: this will create a new issue each time the staging tests fail, which could happen several times (on the cron schedule) before a fix is implemented and applied. I'm not sure if that's worth addressing now.

Might get annoying if staging is broken for a long time, but I figure we can cross that bridge when we get to it.

I'm a bit late but if you want to avoid 3rd party actions, this is also a single call with actions/github-script. Example:
https://github.com/theupdateframework/python-tuf/blob/develop/.github/workflows/maintainer-permissions-reminder.yml

One thing: this will create a new issue each time the staging tests fail, which could happen several times (on the cron schedule) before a fix is implemented and applied. I'm not sure if that's worth addressing now.

Might get annoying if staging is broken for a long time, but I figure we can cross that bridge when we get to it.

when you do, a rough bridge is here: https://github.com/theupdateframework/python-tuf/blob/develop/.github/workflows/specification-version.yml 😉

Nice! Yeah, avoiding a third party action where we can do so conveniently seems like an easy win to me.