You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have read over many posts discussing branches that continue to show in Sourcetree even though they have been deleted from the repository. I understand that this is by design and with intention so as to be non-destructive.
I performed a fetch with prune using Sourctree and that cleaned up my local repositories. The local repo is an accurate reflection of the remote (as seen in the browser interface)
I believe that I am experiencing something similar, yet different. I am using Sourcetree v3.2
If we view the Browser interface, I see four branches in the repo that properly reflect our project. In Sourcetree, the local repo is an accurate reflection of the remote as compared to the Browser UI.
In Sourcetree, I see seven remote branches, three of which don't exist.
If I issue a git command, I also see seven remote branches, three of which don't exist.
git branch -r
I cloned the repository on a different computer, and the clone creates 7 branches, including the three that don't exist.
My question is... What is the source of the references to these old branches, if they don't exist in the remote repository and they get cloned to a clean computer when they seemingly don't exist on the remote?