Different merge policies for different groups

My organization has different groups that contribute to our source repository, and they have two different sets of needs for their pull requests.  For one group, I'd like to a merge check that requires a successful build and gives a default set of reviewers.  For the other group, they won't require a build and they'll enter their own reviewers.  I know for setting the default reviewers I could just have the different groups use different branch names that I could recognize as a pattern.  But for the successful build, I don't see a way to make the distinction.

Any help would be appreciated

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

171 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