Add workflow for creating versioning pr #64
Merged
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
Add create versioning pr Add semver label check
geofflamrock
added
bug
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 introduces the use of
autoas a versioning tool. To indicate that a specific PR requires a new release, add a labelmajor,minororpatch. When the PR is merged a new versioning PR will be created which when merged will trigger the new release to be created.An additional workflow has been added to add a status check onto a PR depending on if there is a proper label or not. At the moment this doesn't really impact anything, it's just an indicator. The default label is
skip-releaseif none is put on the PR, which won't result in a new version.