Is there a way to remove approval if new commit arrives to a pull request?

[Edem]

When I approve a pull request, it stays approved even if there are new commits are added to it before being merged. This means potentially unreviewed code could be merged, since  for another administrator it is not clear that the new commit arrived after approval.

Is there a way to automatically revoke Approvals from a pull request if a new commit is added to it afterward?

[Julius Davies _bit-booster_com_ · Accepted solution]

For Bitbucket Cloud:  it's a premium feature (paid accounts only).  Add a "Branch Permission" and then click on "Merge Checks" within the newly added Branch Permission and select this option:  "[x] Reset approvals when the source branch is modified."

For Bitbucket Server:  install the free plugin: Auto Unapprove for Bitbucket Server.

[Philippe Bourdeau]

One of the most gimmicky features ever.

I wanted to enable this, but on my tier, only "Reset requested changes when the source branch is modified" is available.

"Reset approvals when the source branch is modified" is on a different tier.

They decided to separate the two options, which provide the same utility and are essentially the same feature.

[lee_conlin]

Use github instead - they have this feature as standard.

[Edem]

That's good to know, but since we can't switch to github, this is not a solution - especially since the original question was about Bitbucket.

(If you have a question about your car, you wouldn't like to hear an answer saying "buy a different car", would you?)

[lee_conlin]

Agreed... but then most cars share the same basic functional features... 4 wheels, steering wheel, hand brake, etc.

If you'd asked "I have a car with 5 gears but want to use 6th gear" I might have answered that you need to buy a different car.

IMO this is a basic feature that should be standard in any PR process. Github, Gitlab, etc. all do it but Atlassian have chosen to lock it away behind a paywall... thus my answer is to move to a provider that has it available.

Since you're obviously on a free account, or this wouldn't be an issue, moving to another provider would seem a sensible option and migrating a git repo to another provider and retaining history is relatively easy.

[Thomas Limp]

I know it's more than a year old but I just stumbled over that on.

@lee_conlin your comments are indeed not very helpful :

• not having a premium feature  doesn't mean your not paying (as one also as paid for their 5 gears car)
• you can in no way know for which reasons someone chose a specific service (car)
• therefore you cannot estimate if switching service (buying a new car) is a valid option

You could have just keep your fingers shut since the information "you need a premium plan" was already given.

I am assuming your intent wasn't to be helpful in answering the OP but just to troll Bitbucket for not providing a (IYO) "standard feature". 

Sorry, I had to comment here. I just cannot stand that trolly non-helpful attitude.

[Greg Sanderson]

Guys, no need for emotion. OP asked for something that needed premium (pay money) and an alternative was suggested that is free. Nothing more. If you don't want to swap to github or something else then don't, but if people stopped giving the advice because it's not some 100% direct answer to the precise question, we'd all learn a lot less in general.

Use Github, don't. Buy a new car, don't. It's your choice :)

It's not like lee_conlin suggested using MS word to track code changes and FTP files to live. Using Github is a useful and direct alternative.

[Aaron]

Hello Adam,

Welcome to the Atlassian Community!

It would seem you need a Premium Plan to do this as it mentions in this document here. With the Premium plan you gain access to "Reset approvals when the source branch is modified."

That is for Cloud, if you are using Bitbucket Server the Auto Unapprove for Bitbucket Server is what you are looking for. 

Regards,
Aaron Levinson
Dev Tools Support Engineer