Approval setting

[Zohra Shariff]

What settings can guarantee the that approval is done by another user? 

[Julius Davies [bit-booster.com]]

Bitbucket Cloud:  Use the merge checks feature, in particular the "Check for at least {#} approvals" option.

Bitbucket Server:  You can use the builtin "minimum approval" merge check feature, or if you want to get fancier, try the "Approval Policy" section of our Control Freak app.  Here's its config screen:

[Zohra Shariff]

 But does this guarantee that there are two individuals in the process?  

[Julius Davies [bit-booster.com]]

Out-of-the-box it only guarantees that someone OTHER than the PR creator looked at the code.

As long as the committer always creates the PR, then you're all good.

Hmmm... note-to-self: this is probably something Bit-Booster could further improve with our free Control Freak app (only available on Bitbucket Server and Data Center).  We don't implement anything around this issue at this time, but we might release something for this in 4-6 weeks from today (October 15, 2018).  Something like "don't count approvals coming from committers on the branch to be merged".