Skip to content

add support for custom merge messages without 'TargetBranch' capture group #1846

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Dobriy33 wants to merge 3 commits into from
Closed

add support for custom merge messages without 'TargetBranch' capture group #1846

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0844c02
add support for custom merge messages without 'TargetBranch' capture …
Dobriy33 Oct 6, 2019
517a0bf
Update configuration.md
Dobriy33 Oct 9, 2019
0a3964c
Merge branch 'master' into feature/bitbucket_cloud_merge_msg_support
Dobriy33 Oct 9, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update configuration.md
  • Loading branch information
@Dobriy33
Dobriy33 authored Oct 9, 2019
commit 517a0bfde77807251b57223346011e138428902b
4 changes: 3 additions & 1 deletion docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,9 +193,11 @@ merge-message-formats:

The regular expression should contain the following capture groups:
+ SourceBranch - Identifies the source branch of the merge
+ TargetBranch - Identifies the target of the merge
+ TargetBranch - Identifies the target of the merge (optional)
+ PullRequestNumber - Captures the pull-request number

If regular expression doesn't contain TargetBranch then for matched messages current branch will be used.

Custom merge message formats are evalauted _before_ any built in formats.

## Branch configuration
Expand Down