Issue Summary

When a Pull Request is approved, later changes to the feature branch cause Bitbucket to reset all approvals if the user enables the "Reset approvals when the source branch is modified" merge condition.

Steps to Reproduce

1. Create a Pull Request and add approvers

1. Enable the "Reset approvals when the source branch is modified" merge condition

1. Ask approvers to review and approve the Pull Request

1. The Pull Request is fully approved

1. Make changes to the source branch

1. Observe that all previous approvals are reset without notifying approvers to review and approve again

Expected Results

The Bitbucket UI should offer an option (such as a Reminder button) next to Pull Request approvers to send a notification to review and re-approve the Pull Request

Actual Results

Currently, no notification is sent to approvers, and the Bitbucket UI lacks a reminder option

Workaround

Developers must manually remind approvers, who then leave Bitbucket to message reviewers on Slack or email for re-approval. This causes context switching and merge delays as reviewers aren't promptly aware that re-approval is needed.