Add Git Branch Pattern property #6129
Open
+171
−0
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.
Prerequisites
Description
This proposal aims to give control over the branch name that is extracted, with regular expressions.
I am not familiar with
Go
, but tried my best.In my workflow, I usually have long branch name (such as
feature/PROJECT-12345-scope-of-ticket
), and while interacting in the terminal, I don't really care about the scope. This feature allows me to extract only the issue part, and can still be combined with themapping_branches
.Can't wait to have feedback, and hopefully see something like this in the project, which is great btw, good job !
Question
Is the documentation/schema aimed to be edited by hand ? Or is there anything I missed to handle this automatically ?
I felt it hard to write this part, mainly due to alignment.