Repository navigation
ci(release): publish the release when its pull request is merged - #2
Merged
Merged
Conversation
Merging a release pull request is the decision to release, so nothing should be left to remember afterwards. Opening the pull request stays manual: a push to main must not open or update one until a release is wanted.
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
1 participant
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.
Merging a release pull request is the decision to release, so the tag and GitHub release should follow without a second step. Opening or updating the pull request stays manual (workflow_dispatch). Every push to main now starts a short Release job that does nothing unless a release pull request was just merged.