As a user, I would like to see the branch that a commit belongs to at a glance

17 votes

Currently, when going through the GIT history of a repo, the only way to determine which branch a commit belongs to is to follow its tram track all the way up to the head of that branch, where the name label is clearly displayed. It would be great to make this easier to find, without having to possibly scroll up multiple times, while also keeping our eyes firmly locked on the tram track we're following.

I think we can tackle this with 2 updates:

Display the branch name associated with a tree section when a user hovers over one of the tram tracks, as well as:

Display the name of the branch that a commit belongs to in the right hand information window (where the commit message and commit files are displayed). This could be listed under/over/next to/around the commit hash, or near the parent hash, or just somewhere else in that section.

I believe that these updates would make working with GitKraken much more efficient

Under consideration Suggested by: Luke (18 Aug, '21) • Upvoted: 28 Mar • Comments: 3

Comments: 3

20 Aug, '21
William Penton (Nexxuz)
The problems is that a commit can "belong" to any number of different branches (or none at all in the case of a detached head). The term "branch" is really just a "shortcut to a particular commit" and each commit is just a snapshot of the difference your code base is compared to a different commit.

There are two features that currently exist in GK that could help you though:
1) The "Solo" feature, which shows you only the commits within a single branch.
2) The Show/Hide feature per branch. You can "hide" some branches and "show" others.

I would suggest starting off with the Solo to get an idea of how it works. I would start off with your master/production/main branch that will show you all commits that will be in "production".

Once you get the hang of that then try hiding all branches and then only show master AND development, then you will see how to more easily determine where your commits are located. If you want to discuss further I am "nexxuz" on https://gitkraken.slack.com/
03 Sep, '21
Masih
I miss this feature too. But as a workaround I simply lookup for branches in the branch history that include that specific commit:
git branch -a --contains <commit_SHA>
07 Jul, '22
Seb U.
+1
Same here, wasted much time doing "tram track" riding, scrolling through hundreds of commits.