How to limit who can merge code on a pull request in bitbucket? [closed]

Question

I have a small team of developers that use bitbucket as our git repository.

I want to know how to limit who can merge code on a pull request in bitbucket? AND/OR force at least one approval before the merge can be done. Basically I am looking to force a code review.

As of now the creator of a pull-request (and everyone else) can not only approve but also merge the code in which can be an issue for quality purposes. Thanks in advance.

Update:

Bitbucket now allows for control over push permissions, branch deletion, and history re-writing. The full management instructions are here: https://confluence.atlassian.com/bitbucket/branch-management-385912271.html

There still is not a way to force a minimum number of approvals however.

Answer 1

I want to know how to limit who can merge code on a pull request in bitbucket? AND/OR force at least one approval before the merge can be done. Basically I am looking to force a code review.

This functionality is not available in Bitbucket right now, but Atlassian's behind-the-firewall version of Git hosting has it.

Stash allows you to:

• limit who can change branches

• enforce a minimum number of approvals before merging pull requests (it can do a similar thing for Bamboo builds - i.e. the code must compile before it can be merged)

• reset approvals if a pull request changes

It's a curious asymmetry in Atlassian's own products.