Hi Team,
Whenever we sync our feature branch, then the existing pull request to development branch will not have the changes because that is already present in dev branches. But if there were approvals and then we sync, it will remove the approvals. We do not want it to remove if there are no code changes in pull-request. Please let me know if we can achieve this.
Hi, @Jimmy Seddon Thank you for your comment.
I was expecting this checkbox to be conditional. i.e. unapprove automatically only if the new change is visible in pull-request.
Example, say am working on 'Feature A' branch (created from master) and have commit and pull-request to development branch is open and got reviews. Another person worked on another branch 'Feature B' and made some code changes, then moved to the development branch and then moved to the master branch. Now I will try to sync my branch with master. In this case, I will get 'Feature B' changes into my branch. Since it is also in the development branch, there won't be any new code changes in pull-request to review (not considering the conflict scenario). So, we don't want it to remove approvals.
We are using cloud service.
I don't think there's anything for Bitbucket Cloud to handle this problem - at least not yet. If you were on Bitbucket Server (on-prem Bitbucket) I would tell you to look into two plugins (one free, one paid):
1. Auto Unapprove for Bitbucket Server (free) - changelog for version 2.2.0 shows how it switched its logic to implement dropping approvals as per the logic you're requested here (e.g., sync merges should not cause approvals to drop).
2. PR-Booster for Bitbucket Server (paid) - set the "Automatically Withdraw Approvals" setting to "Yes - For Significant Pushes".
Full disclosure: my company maintains the paid "PR-Booster for Bitbucket Server" plugin.