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.
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:
masteris your default branch) or "Pattern" with "refs/heads/master"
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