Repository navigation
release-tag: promote-branch fast-forwards a branch to the release - #12
Merged
Merged
Conversation
For a hosting service that deploys from a branch: after the tag, the tag job moves that branch to the released commit with the release App's token, so only release merges reach it. A missing branch is created, a re-run passes, and a commit that does not descend from the branch fails; never a force push.
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.
New optional input
promote-branchofrelease-tag.yml: after the tag, the branch is fast-forwarded to the released commit with the release App's token (release.sh promote; created if missing, re-run safe, never forced). For a hosting service that deploys from a branch, so only release merges reach it. Tests intest_release.sh(fakeghwith branch refs andcompare); README updated.