ci: add auto-update-pr flywheel workflow#49
Open
goastler wants to merge 2 commits into
Open
Conversation
✅ Deploy Preview for peaceful-pothos-9e62ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
auto-update-pr.yml— a post-merge "flywheel" workflow.After each merge to
main(plus a 30-min cron backstop and manual dispatch), it:mainthat have auto-merge enabled, oldest first;UNKNOWNcomputation;mergeStateStatus == BEHIND(out of date but otherwise green);PUT /pulls/{n}/update-branch) on that one PR, then stops.Updating retriggers the PR's CI; if it passes, auto-merge merges it, which fires another push to
main, which updates the next stale PR — a self-sustaining flywheel that unblocks auto-merge PRs stuck on being out of date.Why one PR per run
Updating every stale PR at once makes them all up-to-date simultaneously: the first merges, the rest go instantly stale again, and a full CI run is burned on each for nothing. Updating one at a time keeps CI spend proportional to merges.
Notes
PROSOPONATOR_PAT(not the defaultGITHUB_TOKEN) so the branch update is attributed to a real user and therefore retriggers the PR's CI. The default token would not.concurrency: auto-update-pr(no cancel) single-flights runs so simultaneous merges can't double-spend CI.mergeStateStatus == BEHIND, which requires "Require branches to be up to date before merging" to be enabled in branch protection.