### Problem to solve It can sometimes be confusing to determine the order of the commit-list in a merge-request. ### Target audience I'm sorry, I can't really fill this out as specified in the template, because the [link to the personas](https://design.gitlab.com/getting-started/personas) return 404. Please advice :) ### Further details While commit-order with most recent commit on the top is the de-facto standard for showing commit-lists in Git tools, it seems like it's not *completely* universal. In particular GitHub shows the commit-list on pull-requests sorted by timestamp rather than commit order, and with the most recent commit on the bottom. This makes it confusing for users used to GitHub's ordering to read merge-requests in GitLab. ### Proposal We can make this immediately obvious by including the commit graph next to the commit-list, decorating it with the branch name at the tip. ### What does success look like, and how can we measure that? I'm not sure this is directly measurable. ### Links / references https://lists.freedesktop.org/archives/mesa-dev/2019-January/213659.html