ci: retrigger automerge for open release PRs on push to main#449
Merged
Conversation
When main advances without a new commit landing on the release-please PR branch, no synchronize event fires and the automerge never re-evaluates. This workflow dispatches the automerge for every open release-please PR after each push to main, closing that gap. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
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.
Problem
When
mainadvances (e.g. a feature PR merges) without a new commit landing onthe release-please PR branch, no
synchronizeevent fires and the automergenever re-evaluates. The release PR can be left unmergeable or simply stale until
someone manually dispatches the automerge.
Fix
New workflow
release-please-automerge-retrigger.ymltriggers on every push tomain, finds all open release-please PRs, andworkflow_dispatches theautomerge for each one. The automerge itself is idempotent (it skips if already
merged, not a release branch, version unchanged, etc.), so dispatching it
multiple times is safe.
Test plan