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

How can I hide merged branches from SourceTree graph?


We use git flow, so we do work in feature branches, and we maintain release branches too. When they're finished, they get merged back into `develop`.

Over the past 12 months, about 20 branches have been merged into `develop`, so the graph is getting pretty hard to read - basically useless. See the attached screenshot.


Is there any way to hide the merged branches, but still see unmerged branches?


Screen Shot 2018-06-04 at 08.51.06.png

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 05, 2018

There is an option to select the current branch or any individual branch if you want a filtered graph and history. Does that help?

I know this is old, but that doesn't help at all.  The reason being is that hides all branches.  If I understand the parent correctly (and my needs), we want to hide only merged branches but still show all unmerged branches in the graph.

It's really frustrating because I love source tree (especially because of this beautiful graph feature).  But when you have a bunch of merged in feature branches that are no longer relevant it becomes useless.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events