Negation in Branch permission patterns

Hello

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 12, 2018 in Bitbucket

Do you use any Atlassian products for your personal projects?

After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...

175 views 20 8
Join discussion

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