Repository navigation
Merge a release's back-merge once TagBot has tagged the release - #65
Merged
Merged
Conversation
With the input `auto-merge`, the back-merge workflow approves a release's back-merge as github-actions[bot] and merges it with the ReleaseFlow app's token, or RELEASEFLOW_TOKEN, once TagBot has tagged the release at the commit that the back-merge brings, GitHub's state of it is clean, and it doesn't conflict. It waits for the tag because the back-merge's merge commit may have the release's tree, which TagBot could otherwise tag instead of the release's commit. It runs on the caller's `workflow_run` of TagBot and of the required checks, and skips the other pull requests' checks; GitHub's auto-merge isn't used, so nothing else can merge itself. Each run reports, in its notices and job summary, what each back-merge waits for, and names the setting or permission to change where approving or merging is refused; the README lists these under Troubleshooting the back-merge. This repository's own back-merges use it.
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.
With the input
auto-merge, the back-merge workflow approves a release's back-merge as github-actions[bot] and merges it with the ReleaseFlow app's token, or RELEASEFLOW_TOKEN, once TagBot has tagged the release at the commit that the back-merge brings, GitHub's state of it is clean, and it doesn't conflict. It waits for the tag because the back-merge's merge commit may have the release's tree, which TagBot could otherwise tag instead of the release's commit. It runs on the caller'sworkflow_runof TagBot and of the required checks, and skips the other pull requests' checks; GitHub's auto-merge isn't used, so nothing else can merge itself.Each run reports, in its notices and job summary, what each back-merge waits for, and names the setting or permission to change where approving or merging is refused; the README lists these under Troubleshooting the back-merge. This repository's own back-merges use it.