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

Entire folder of local branches missing from left hand pane in Sourcetree

I just noticed today that my UI in Sourcetree seems to be broken, but I can't seem to narrow down why.

I usually name my branches `andy/branch-name...`  and sourcetree is very good at nicely organizing them into sub-folders.  Today though, I noticed that my folder no longer had an expanding arrow,  even though all the local branches still exist and work fine when I use the git command line.  They are even accessible through the commit log in Sourcetree.

Sorry for the highly obfuscated screen capture, but what you are seeing is the left pane of source tree.  The long list of branches on the right is from the branch selector at the top of the graph display showing all local branches.

Screen Shot 2019-03-10 at 10.56.48 AM.png

I have tried the instructions to wipe my sourcetree config to the defaults (by removing all the files within the `Application Support/Sourcetree` folder.  I have also tried removing and re-installing Sourcetree without any luck.

Guess I am back to using the command line!

1 answer

1 accepted

0 votes
Answer accepted

Apparently I was able to jig it back into place by creating a new branch within the folder based off an existing branch in the folder.

This seems to have made the sidebar folder expandable again and have it have the right content in it.

I've just had the same thing happen all of my "feature/" branches have disappeared locally, but still working remotely. Restarting Sourcetree doesn't solve it, neither does creating a new branch from the current branch (which is a feature/ branch).

Any ideas?

Andy Chute's suggestion worked for me. 

However, when I then immediately deleted the branch the issue returned like before.  Additionally, deleting any other branch also seems to trigger the loss of all branches from view.

The only possible specific cause that I can think of is that I believe that the issue first happened when I deleted the top branch in the whole list, so perhaps there is a zero-index bug.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events