feat: add support for auto semantic release #77
Conversation
This file contains 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
|
How does this work on a go repo? @AyodejiO |
This just creates the next release/tag (in GitHub) upon merging to master. Uses the commit rules here to determine the next SEM version. I expect the go pkg to get auto updated when there's a newer sem version. @unicodeveloper |
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.
This PR adds support to create new semantic release versions when new changes are merged into the master branch.
This enforces standard commits messages to create new releases.
See here:
https://github.com/semantic-release/commit-analyzer/blob/master/lib/default-release-rules.js