<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=515857) </details> <!--IssueSummary end--> ## Problem to Solve When using the setting to reset approvals, the behavior is controlled by `patch-id`. This means that approvals are not always reset, but only sometimes if the content has changed. This can be confusing because it's not clear when or why approvals have been reset. ## Proposal We currently provide a system note when approvals are reset, we should consider: 1. Adding a system not that shows the `patch-id` after each push so that you could determine if it has/has-not changed 2. Exposing the `patch-id` in some other place in the UI