Enable auto-merge on release PR after deploy#6363
Merged
Merged
Conversation
- Add `all-tests-succeeded` gate job separate from `all-tasks-passed` - Reorder `deploy-tag` workflow: deploys run first, `make-release` last - Add `enable-auto-merge-release-pr` as final job in `deploy-tag`, requiring all other jobs before enabling GitHub auto-merge - `all-tasks-passed` on release branches now gates on `tag-release-branch` so it stays pending until the release is approved and tagged - `approve-release` requires `all-tests-succeeded` (not `all-tasks-passed`) Depends on RevenueCat/fastlane-plugin-revenuecat_internal#115 Made-with: Cursor
The Pluginfile and Gemfile.lock changes are not needed in this PR. The dependency on the new plugin action will be satisfied once fastlane-plugin-revenuecat_internal#115 is merged. Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
tonidero
reviewed
Feb 27, 2026
| name: All tests succeeded | ||
| command: echo "All tests succeeded" | ||
|
|
||
| enable-auto-merge-release-pr: |
Contributor
There was a problem hiding this comment.
Could be worth moving these to the orb? Happy to merge and move later though.
Member
Author
There was a problem hiding this comment.
Oh yes, You're right! Great suggestion!
Member
Author
There was a problem hiding this comment.
tonidero
approved these changes
Feb 27, 2026
This was referenced Mar 4, 2026
facumenzella
pushed a commit
that referenced
this pull request
Mar 5, 2026
* Enable auto-merge on release PR after deploy - Add `all-tests-succeeded` gate job separate from `all-tasks-passed` - Reorder `deploy-tag` workflow: deploys run first, `make-release` last - Add `enable-auto-merge-release-pr` as final job in `deploy-tag`, requiring all other jobs before enabling GitHub auto-merge - `all-tasks-passed` on release branches now gates on `tag-release-branch` so it stays pending until the release is approved and tagged - `approve-release` requires `all-tests-succeeded` (not `all-tasks-passed`) Depends on RevenueCat/fastlane-plugin-revenuecat_internal#115 Made-with: Cursor * Remove temporary plugin branch pin The Pluginfile and Gemfile.lock changes are not needed in this PR. The dependency on the new plugin action will be satisfied once fastlane-plugin-revenuecat_internal#115 is merged. Made-with: Cursor * Remove outdated comment above all-tasks-passed Made-with: Cursor * Strip trailing newline from .version when building branch name Made-with: Cursor * Use orb job for enable-auto-merge-release-pr Made-with: Cursor
This was referenced Mar 6, 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
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.
Checklist
Motivation
After a release is tagged and all deploys finish, the release PR into
mainstill requires manual merging. This automates it by enabling GitHub auto-merge on the release PR once all deploy jobs succeed.Description
all-tests-succeededintermediate gate (split fromall-tasks-passed) to separate the test gate from the release gate.deploy-tagworkflow somake-releaseruns after all deploy jobs (they only need the git tag, not the GitHub release).revenuecat/enable-auto-merge-release-pr(from the shared orb) as the final job indeploy-tag, requiring all other jobs. It uses theenable_auto_merge_for_prplugin action to enable GitHub auto-merge on the release PR.all-tasks-passedon release branches now gates ontag-release-branch, keeping it pending until the release is approved and tagged. Once auto-merge is enabled and this check passes, the PR merges automatically.approve-releasenow requiresall-tests-succeededinstead ofall-tasks-passed.