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 form feature/SAMPLE_123-foo-bar, where the project slug is SAMPLE to signify issue SAMPLE-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.
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.