Update release flow to branch from develop and merge into master#194
Closed
bartes wants to merge 1 commit into
Closed
Update release flow to branch from develop and merge into master#194bartes wants to merge 1 commit into
bartes wants to merge 1 commit into
Conversation
Update RELEASING.md so releases start from develop and add the step to merge develop into master and push before tagging and publishing.
Contributor
Author
|
Folded into #195 (the RELEASING.md change is cherry-picked onto that branch). Closing in favor of the combined PR. |
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.
Updates
RELEASING.mdto reflect the develop/master branch model.developinstead ofmaster.develop.develop, merge it intomaster, and pushmastertooriginbefore creating the GitHub release and publishing to npm.