How to give logical conditions in branch permission


I need to restrict master and release/* branches to avoid "deletion, rewrite history, changes without PR" and I've tried this "master|release/*, but didn't work for me. Is it possible for me to combine these two in a single rule? I know I can give separate rules, I'm looking for more optimized solution.


2 answers

1 accepted

This widget could not be displayed.

Hi Bijoy, 

you will need to create 2 separate branch permission rules, there is currently no way to do it in a single rule. If I may ask, why are you trying to put both in the same rule?

The pattern matcher in Bitbucket Server does not support the full regex syntax, see the Branch permission patterns page for details.

For the use-case you describe, you can create the following permissions: 

  • "Branch model" for the "release" prefix or "Pattern" with "release/"
  • "Branch" for "master" or "Branch model" development branch (if master is your default branch) or "Pattern" with "refs/heads/master"



This widget could not be displayed.

Hi Felix

Thanks for the quick response. We used to use regex for other hooks and I've tried the same here also and didn't work.So decided check with Atlassian, that's it. I'm OK I can create multiple rules.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

1,207 views 8 11
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you