For a given repository, we have two ways of setting minimum number of reviewer approvals to get a pull request into a mergable state. In the Default Reviewers settings page one can enter the number of Approvals Required. In the documentation for this you state: In the Approvals required field, select how many reviewers must approve pull requests that match this criteria before merging.
This does not appear to do anything. To get an actual barrier between pull requests and merges, one must set Requires Approvers field in the Pull Request setting page.
Seems to me these two fields should be linked. If I set the Approvals Required field in the Default Reviewers settings page, that setting should be forwarded to Requires Approvers field in the Pull Request setting page.
Hi Jaye, enabling just one of them should be enough. Can you let us know which version of Bitbucket Server are you using? Also, can you send us the following screenshots?:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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!
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