Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

SourceTree: What do colors of Branches and Tags mean?

Do the color of branches and tags within log-view do have any special meaning?


3 answers

1 accepted

4 votes
Answer accepted
KieranA Rising Star Jun 11, 2013

Hi Johannes,

They have no meaning at all, they're only there so you can easily distinguish between different branches and tags.

The colours change when you change branch because a branch doesn't hold any state by which we determine a colour, we just calculate unique colours when the view initially loads.

Hope that helps

That's something I assumed. In my eyes I might be useful to use some more colors than four only - looking on the example above it might be assumed at a first look, that the yellow ones are related to each other (green also). The red ones ARE actually related as they all refer to the same branch ....

Like Alves Christo likes this

At least i would expect that develop branch is in whole tree shown with same color. Sometimes it is not. It is really confusing when one branch is in one specific timeline span blue then few commits after pink (and some other branch take blue color)..

This is mainly an issue of git and how it handles branches. Have a look at my (answer here)[]. *develop* is not a special branch for git in any way - it's a normal branch like each other branch. So why should it be treated specially by git when rendering trees,created via git-log?. Branch *develop* gets it's special meaning by the branching model you use (for example gitflow ...). What you are asking for is a graph rendering depending on the applied branching model. As the branching model could not be enforced in any way (it's only a recomendation) via the used tools (git/sourcetree) it does not make sense (in my eyes) to render the graph using assumptions from a branching model which is not sure/enforced to be used ...

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.

Like Andrew Leckie likes this

I agree with Lewis.

Like Andrew Leckie likes this

or give ability to select colors 

Like Andrew Leckie likes this

Yes, please allow for selecting colors.

If this is too much trouble, at least show a legend explaining what color belongs what branch.

Like # people like this


Agree with Lewis

Like Andrew Leckie likes this
Deleted user Nov 06, 2016


Also a +1 to Lewis, although I'd prefer to just be able to specify colors for my branches independently.

For example, allow us to tell source tree:

"Any branch called 'MyRandomBranchName' should be rendered as blue"


"Any branch called 'feature' should be rendered as a green line"

I would imagine that this could be done by changing only the GUI logic of the program. It would be a very nifty feature.

+1 please make branch colors in some way consistent. I'll take git flow or manual.

Our team has grown and now my tree is so full of changing colors (and position as well!) that I now have lower comprehension of the situation. 

Like Andrew Leckie likes this


The color graph is useless right now.  Being able to map specific colors to specific branch names would be a godsend!  


Considering this has been an obvious pain point since 2013, I won't hold my breath. 

Like Andrew Leckie likes this

Adding a +1 here!  Even a best-effort color preference would be super useful.. and a legend on the commits view seems like it would be easy to do and very useful.

I haven't even discovered the need for colors and want to pick my own. Please, sweet Atlassians - make this so!



+1, wtf Atlassian it's 2020 please fix!!!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events