Allow configuration of the separator character (+) in git-tag-commit and version-commit
#54
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
…t and version-commit
lukemelia
approved these changes
Mar 2, 2017
Contributor
|
Thanks @reidab! |
|
Can you release this @lukemelia ? It's breaking my builds because of a Sentry update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What Changed & Why
This allows for the
+symbol in the git-tag-commit and version-commit strategies to be configured by the user.Why? The error reporting service I'm using at work (Sentry) recently changed the validation for what they consider valid release identifiers and the new format disallows
+.PR Checklist