Auto-trigger release workflow on prepare-release PR merge#571
Merged
Conversation
The "Prepare release" workflow auto-merges its PR once CI passes; hooking the release workflow to that merge removes the manual step of dispatching it afterwards. Belt-and-suspenders `if:` filters reject fork PRs and non-Linguist authors, so only the auto-generated `prepare-release` PR can trigger a release. Manual `workflow_dispatch` is preserved for re-runs and dry-run testing. Pattern documented in heroku/languages-github-actions#358.
edmorley
approved these changes
May 18, 2026
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
2 participants
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.
The "Prepare release" workflow already auto-merges its PR once CI passes. Hooking the release workflow to that merge removes the manual step of dispatching it afterwards.
Belt-and-suspenders
if:filters reject fork PRs and non-Linguist authors, so only the auto-generatedprepare-releasePR can trigger a release. Manualworkflow_dispatchis preserved for re-runs and dry-run testing.Pattern documented in heroku/languages-github-actions#358; first applied (and validated end-to-end) in heroku/buildpacks-dotnet#425.