<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal When we're comparing commits between branches, it's hard to know the commit-related info since GitLab only shows the number of commits in the main branch (i.e master) but none in other branches. It would be helpful to also show the commit-related info in other branches, along with the last commit code and when this commit was done. It would be even better if GitLab can show how many commits a branch is behind/ahead the main branch. So, for example one changes to another branch, say branch "foobar", she can see: "This branch is 20 commits ahead, 3 commits behind master" Additionally, we can also know the following info: "[userName] [commitMessage] [commitCode] [commitDate] [number of commits]" i.e "LinusTorvalds [BugFix] Add Mac compatibility driver 122f45f on Dec 12, 2021 200 commits" <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->