Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Override default reviewers settings for specific branch pattern

kamil_
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2019

Hi there!

In our Bitbucket project we would like to have one branch name (pattern) that does not require review from other team members (as changes there are very trivial and it's nearly impossible to make a mistake).

Our current configuration is: 

Source: any branch, Target: any branch, default reviewers: me and my colleague, approvals required 1.

Now, after having that general rule above and setting up additional one with e.g. branch name "upgrade" and 0 approvals required I was hoping that the latter (more precise) will come into play when I open PR from "upgrade" branch. Surprisingly I couldn't merge my PR because of required approval.

I tried to play with order of default reviewer rules, but it didn't help either. Does it all mean that every single default reviewer setting must be fully disjoint in terms of branch pattern/name? Does anybody has solution to that problem?

1 answer

0 votes
Yevhen Rohovets
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 12, 2019

As far as I understand how this works, if you create a branch that does not require approval from a branch that requires approval, then you will not be able to merge your PR until there is approval from the parent branch.

But I’m not a true master of Bitbuckets, maybe my colleagues will tell you an elegant solution

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events