<!--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=558736) </details> <!--IssueSummary end--> <!-- This issue template can be used as a great starting point for feature requests. Learn more about the process: https://handbook.gitlab.com/handbook/product/product-management/#customer-feature-requests. The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve Next and previous commit buttons are placed at the top of page in MR changes view. It is easy to quickly move between commits, but when doing a review of MR and looking at each commit in a row - after reviewing a commit you end up at the bottom of page, and you need to go all the way up to top of page to press next commit button. Especially if commit has big diff, or many files - scrolling up after each commit can become annoying.  ### Intended users Developers, Reviewers. ### Proposal When "Show one file at a time" option is disabled - duplicate "previous commit" and "next commit" buttons at the bottom of page, the same way as next and previous file buttons are placed when "Show one file at a time" option is enabled.  ~"type::feature"