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

439 views 6 9
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