How to know which branch color correlates with which branch

[Christoph Schmidpeter]

In SourceTree the log shows for each branch a random color. How do I know which color identifies which branch? The leftmost one is the master branch, or is it the current branch?

How to identify the other colours? Maybe I am too blind, but I just cannot find a caption table for it showing which branch relates to which color. Where can I find such thing in SourceTree?

Thank you for your help in advance!

[Johannes Kilian]

How do I know which color identifies which branch?

What do the colors mean?

see:

• https://answers.atlassian.com/questions/179335/sourcetree-what-do-colors-of-branches-and-tags-mean
• https://answers.atlassian.com/questions/258200/what-does-the-green-dots-in-the-graph-mean
• https://answers.atlassian.com/questions/271836/branching-problem-sourcetree

The leftmost one is the master branch, or is it the current branch?

"master" is just a simple branch in git and nothing special (it just happens to be the default name for the initial branch when creating a new repository). "master" does not even have to exist in a repository - as I said: "master" is just a simple branch as every other branch and nothing special. (see: http://stackoverflow.com/questions/3623755/why-does-my-git-branch-have-no-master).

Any other branch can be configured to be the default branch. Saying this, it does not make sense to have master branch displayed always leftmost.

The git log command never (at least I haven't seen it) shows the static topological relations of the current repository but rather a branch centric view, showing the commit history of the current branch (displaying the evolution of the current branch). At the moment a user has a branch checked out, this is the branch he is focused to - doing a "git log" at this moment, git takes the view of the user and offers a branch centric view with the current branch leftmost ... (Therfore the view is not static - but depends on which branch you are currently considering)

[Timothy Chin]

The leftmost one is the master branch, or is it the current branch?

In SourceTree, the left most brach is always the head.

How to identify the other colours?

I guess it's easier to identify the branch's color by clicking once on the branch in the left bar.

[Christoph Schmidpeter]

I guess it's easier to identify the branch's color by clicking once on the branch in the left bar.

Do you mean where it says

|>File Status

|>Branches

....

?

It does not show all branches. In my repository it shows only master and FeatureBranch1. It does not show any remote branch. Even when I remove all remote branches, there are still many branches which are not shown there but in the log as distinct color.

[Nicholas Nicholas]

Someone else mentioned this on another thread but I think it would be a great idea.

"It would be a nice option to allow the user to select "git flow" colors be used to color branches according to the "git flow" model, i.e. Master=blue, hotfix=orange, release=green, develop=yellow, feature=pink."

While one could argue that the there is nothing special about "master" I have configured GIT flow. The random color thing stinks.

[Danny Idryo]

Whether the colors are random or not - I'd like to know which branch this is that got merged or is left orphaned... How do I see the branch name from the color graph?

[Lyubomyr Vyhovskyy]

+1

[D Vargas]

June of 2016, still no valid answer to such a simple question.

[Gabriel Fortuna]

I have the same question. Seems like a basic bit of functionality; knowing the name of a branch.

Very puzzling, and a huge UX misstep.

[Peter Schneider]

The names of the branches are visible in little colored tags in the description column of the Log/History view. The color of the tag corresponds to the color of the branch line in the Graph column. Remote tracking branches have no line on their own, but commits to them get a tag of equal color. These colored name tags are next to the last commit on the given branch, so one must scroll down for branches with little activity (but OTOH the important information -- branches with recent activity -- is prominently displayed). The branches appear to be ordered by the time of the last commit, left to right from most recent to least recent.

[lennard.berger@student.uni-tuebingen.de]

Once you have a more complex source tree, the UI is basically useless (e.g, what the hell is the base branch here?) 

[Peter Schneider]

My guess is that this repo would be hard to manage with any tool. Try closing a branch once in a while ;-).