chore: Automating the release publish step #366
Merged
Conversation
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
lahirumaramba
approved these changes
Apr 28, 2020
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.
Based on the last release experience I wanted to see if we can further simplify and automate our release flow for Go. The existing workflow requires 2 PRs to carry out a release (one to update the version in dev, and another to merge dev into master). This change attempts to combine our separate staging and publish workflows into one (similar to our other Admin SDK repos).
release:publishlabel to the PR along with setting a specific title pattern.devbranch.devbranch is automatically merged into themasterbranch during release. This requires an access token with write privileges over the master branch. I'm going to work on procuring one for this repo.