How to stop a pull request from being merged?

Question

In our BitBucket configuration it is possible to add changes to the pull request and merge it after the initial approval is given.

The scenario:

1) Create a pull request from the dev branch to master

2) Approve it by someone else

3) Push more changes to the same branch dev branch. The changes now appear in the same pull request

For some reasons, the new changes do not require an approval and can be merged now along with the main change.

Can we change BitBucket configuration in such a way that every new change to the pull request resets the number of approvals to zero?

jredmond · Answer

If you can tag this question (and any future ones) as "bitbucket-server", then that will help clarify things for the people answering them.

Julius Davies _GitBoost_com_ · Answer

The free Bitbucket Server Auto Unapprove Plugin probably does what you're looking for.

It's free, open source, and maintained by Atlassian.   In a couple weeks I'm hoping it will stop dropping approvals for immaterial changes (like clean rebases, clean synchronization merges, amended commit messages, etc).

- Sylvie

(I'm the author of the paid Bit-Booster for Bitbucket Server add-on. If you check out my add-on, you'll see why I decided to send a pull-request to the Unapprove add-on.   Customers were reporting bugs against *my* add-on to say my Rebase button was dropping their approvals!)

Kirill Shmelev · Answer

Unfortunately, we use our own local installation.