Draft: Store and reference SHA at time of approval
requested to merge 415498-codeowner-approval-did-not-get-removed-after-amending-the-commit-and-force-pushing into master
What does this MR do and why?
This Draft MR proposes storing the SHA at the time the user approve a MR, so we can reference that when new code is pushed to determine if we should remove the approval.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to:
Edited by Ash McKenzie