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.
Context
While the
issue_regexp
is helpful, it doesn't solve all of the issues around various naming conventions. For example, my team often ends up with branches in the formfeature/SAMPLE_123-foo-bar
, where the project slug isSAMPLE
to signify issueSAMPLE-123
.I debated a little bit if it made more sense to just have a static
normalize
option, vs a way to pass in "replace" characters, and I'm open to reverting back to that or another suggestion. The main goal here is to just made it a bit easier to get a proper pattern match to a JIRA issue. Often the thing I see most is a space or an underscore instead of the expected dash between the project slug and issue #.Testing
I forked this repo, and released a version of it to test with myself.