<!--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=391454) </details> <!--IssueSummary end--> With MR approval rules configured on a project, including setting `Remove all approvals`, when approvals have already been provided for the code changes in the MR, if a subsequent code change is made, the MR requires approvals again, regardless of where in the code the changes were made. For example: If there are code changes on say lines 20 - 30, and approvals in the MR has been provided based on the MR approval rules, then if there are further changes to code on say lines 120 - 140, the previous approvals are removed, where all approvals need to be provided again. There doesn't seem to be a way to just require approval for the lines of code that changed, so in the example above, since lines 20 - 30 were previously approved, approval should only be needed for the recent changes on lines 120 - 140. Not having the ability to track approval based on specific changes requires approvers to re-approve changes that were previously made, instead of requiring approval for just the specific changes that were made after the initial changes and approvals.