CI Reruns

[SirLouen]

Following this conversation in Slack:
​https://wordpress.slack.com/archives/C04EWKGDJ0K/p1766416737463589?thread_ts=1766176828.042709&cid=C04EWKGDJ0K

@zieladam suggested:

you’d need to trigger the CI build somehow, e.g. push to that PR or start a new empty PR with that PR as a base
some repos allow you to click “re-run CI jobs” in this part of GitHub: ​https://github.com/WordPress/wordpress-develop/actions/runs/14889344575?pr=8514
but not wordpress-develop apparently, at least I can’t do it
it would be convenient to have something in CI to observe labels and trigger CI when, say [CI rerun] label is applied or removed
I’ve seen that done once in some repo and it was pretty cool

Basically the problem here is that when a PR is untouched for a while, the build expires. We need to trigger a CI rerun to rebuild it to run it and test it in Playground again. Ideally, this could be done via Labels.

[swissspidy]

A label-based approach sounds a bit overkill to me. For stale PRs like this I would just merge in the latest changes from trunk to get a more accurate build.

Edit:

you’d need to trigger the CI build somehow, e.g. push to that PR or start a new empty PR with that PR as a base

some repos allow you to click “re-run CI jobs” in this part of GitHub: ​https://github.com/WordPress/wordpress-develop/actions/runs/14889344575?pr=8514
but not wordpress-develop apparently, at least I can’t do it

FWIW, you can't do it for old actions runs like this (> 3 months).

A label-based approach wouldn't help with this either.

[SirLouen]

@swissspidy problem is that will require write access.
With a label based system with triaging access it could be more easily managed for a wider audience, similarly to GB repo