When enabling the merge check plugin, I'm trying to run checks only for feature and bugfix branches (standard Bitbucket naming convention) but can't seem to get the regular expression to pick them up
I'm thinking something like this:
(feature|bugfix)/(.*) as we don't know what the branch is going to be called, only that it is going to start with bugfix/ or feature/
In fact, if I set the field to 'develop' or empty then for a branch named '
feature/WFBO-4160-update-etailers-welcome-fullname' the merge protection starts working. Is the description of the field wrong and it's actually which branches do you want to ignore rather than enable?
It does thanks. Maybe the text that says:
"Only branches, which will match this regular expression will be handled by the hook. If a branch does not match, the hook will skip the evaluation."
Could be changed to
"Only target branches of the merge which match this regular expression will be handled by the hook. If a branch does not match, the hook will skip the evaluation."
As that is much clearer to me?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs