Details
-
Bug
-
Resolution: Obsolete
-
Medium
Description
From BCLOUD-15146
the original problem which led to the creation of this issue:
repository settings: premium features with requiring pull request approvals before merge, and reset approvals on change
- User A creates a pull request on a branch : PR1
- User B approves PR1
- User A makes a new commit to the branch: because of "reset approvals on change" PR1 is not in "approved" state any more
- User B approves PR1 (again)
- User A is not notified about the second approval