<!--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=15724) </details> <!--IssueSummary end--> ## Description It's sometimes difficult to do code review on merge requests when there are many changes, and when the motivation for those changes isn't clear. ## Proposal I propose making it possible to show "blame" in the merge request diff, so that each change is effectively annotated by the commit message which made it. This may only make sense to me, as my habit is to make many microcommits along a branch, such that they explain each change I've made - so any feedback welcome. (Possibly the better solution is just to comment code properly.) ## Mockup