<!--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=537880) </details> <!--IssueSummary end--> ### Proposal The [next/previous commits feature in merge requests](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/39380) is a really nice feature. However, attempting to start reviewing per commit over merge request versions is (subjectively) not intuitive for users. If a merge request includes a stack of patches/commits (for whatever reason it needs to stack), a reviewer who jumps to the `Changes` tab to start reviewing may be overwhelmed by such a change set. If a user inspects the changes compare actions trying to perform a commit comparison, there is no immediate option to do so: {width=684 height=198} The only way to jump to a commit comparison is to venture to the `Commits` subtab then select a random commit. This should then move back to the `Changes` tab and show to a user the active commit being inspected and the ability to move to next/previous commit(s): {width=1061 height=291} It would be nice if the `Changes` tab had an easy way to enable the commit navigation directly. For example, adding a `Compare Commits` button in the scenario that a merge requests has more than one commit: {width=986 height=369} In a similar style as when viewing a version change and the ability to move back to the "all changes" comparision: {width=1177 height=516} ### Links / references - https://gitlab.com/gitlab-org/gitlab-foss/-/issues/39380 - Example (https://gitlab.com/jdknight/git-mr-multi-commits-diff/-/merge_requests/1/diffs)