Skip to content

ci: retrigger automerge for open release PRs on push to main#449

Merged
slydlake merged 1 commit into
mainfrom
ci/automerge-retrigger-on-main-push
Jun 25, 2026
Merged

ci: retrigger automerge for open release PRs on push to main#449
slydlake merged 1 commit into
mainfrom
ci/automerge-retrigger-on-main-push

Conversation

@slydlake

Copy link
Copy Markdown
Collaborator

Problem

When main advances (e.g. a feature PR merges) without a new commit landing on
the release-please PR branch, no synchronize event fires and the automerge
never 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.yml triggers on every push to
main, finds all open release-please PRs, and workflow_dispatches the
automerge 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

  • Merge this PR, then verify the retrigger fires when the next commit lands on main
  • Confirm it dispatches for PR #447 (wordpress 5.0.1) if still open

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>
@slydlake slydlake merged commit 262cb74 into main Jun 25, 2026
6 checks passed
@slydlake slydlake deleted the ci/automerge-retrigger-on-main-push branch June 25, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant