Extend regex to match bitbucket merge commit message #656
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.
Is your feature request related to a problem? Please describe.
Merge commits produce messages which, by default, should match the regexp specified in
mergedBranch
(called byorg.ods.services.GitService.mergedIssueId
) which is used to automatically retrieve the issue Id from the message. However, the message Bitbucket produces by default does not match the expected format.Example of a matching message in previously seen merge commits:
Example of a current non matching message created by Bitbucket in a merge commit:
The matching group is the branch name
feature/ISSUE-456
.This issue has been found when following the "cleanup preview resources" part of the documentation, and uses the newer context property
gitCommitRawMessage
introduced after #587.Describe the solution you'd like
The regexp has been extended to include the new format (preserving backwards compatibility).