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

0 votes
Accepted answer

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"



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 Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,961 views 7 10
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