Negation in Branch permission patterns


We are working in a scenario with multiple Projects (with different project Keys) where developers from other Projects will have to make changes in a repo of another Project.

Because of safety critical SW we want to make sure nothing is merged to develop by "externals"  without being noticed. The goal would be to allow all Project developers to work as usual (PR to develop, no Default Reviewer). Developers from external Projects on the other hand should not have the possibility to merge to develop without an approval of a default reviewer who is member of the project.

This is why when setting up the branch permissions and default reviewers I am looking for an option to negate the branch expression. -> All branches that do not contain the "allowed" Project key will have default refiewers.

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

1,756 views 1 5
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