![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Initial Version and Version 1 of Ticket #64444, comment 1
- Timestamp:
- 12/22/2025 04:02:09 PM (7 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #64444, comment 1
initial v1 1 1 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. 2 3 Edit: 4 5 > 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 6 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 7 but not wordpress-develop apparently, at least I can’t do it 8 9 FWIW, you can't do it for old actions runs like this (> 3 months). 10 11 A label-based approach wouldn't help with this either.
