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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,410,328
Community Members
 
Community Events
169
Community Groups

Branching problem sourcetree

Hello,

all of the sudden the developer branch is not "marked purple" anymore and is not "branching off" but in line with the master branch (see image http://note.io/PsqqK0)

What happend and how can I fix that?

Thanks

3 answers

1 vote

See here: What do the colors of Branches and Tags mean?

Seth Rising Star Mar 12, 2014

I knew I'd seen this before. Good link!

I remembered the link because it was my question ... ;-)

1 vote
Seth Rising Star Mar 11, 2014

That is the standard way SourceTree will draw the graph in your situation. A branch will be drawn directly above the branch it was branched from unless/until the source branch receives another commit (you can test this by checking out master and committing anything).

One positive outcome is that anytime a branch is drawn this way, you can expect a merge from development back to master to be fast-forward, unless you check the option to force a new commit.

It should also be noted that the colors of the branches are completely meaningless. They are only user to help visually follow the history of a branch in cases where you have multiple parallel branches.

'Master' is not really a special branch - it's just a kind of naming convention for the main branch. Any branch may be promoted to be the main branch.

See here:: Why does my 'git branch' have no master?

I assume: As any branch might be the main branch, the branch currently checked out is usually drawn as main branch ("straight history line"). This is true from a user point if view: the currently checked out is currently the branch he is focused on ...

Thanks a lot guys - I think I understand the issue now.

I will try and update in case it doesn't work for me.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events