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
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
There are three branches that appear on the GitHub UI (X, Y, and master). But SourceTree shows me SomeOldBranch and master. I have tried every sequence of fetching, refreshing remote status, and checkout that I can think of. It never gives me the option to checkout either of the new branches X or Y.
Is it possible to force SourceTree to get the list of branches available on the remote? (Something like "git ls-remotes --heads")
I have been trying to check out this new branch for a few hours now. I keep hoping that SourceTree will just work, like it has in the past, but it must be stuck in the past.
The problem is muffled for now, since I found a workaround, but I am curious what was going on. So, treat this as low-priority :) I can mail you a tarball if you like. Here is a gist that compares the horked and working versions of the trees. https://gist.github.com/johnsogg/7fe36aeda500e99e0e3c
This is most likely something to do with my own lack of git-fu.
If you can't figure out what was wrong with it, if you can give us a copy of the repo to diagnose we'd be happy to take a look, in case there's some odd edge case that we should actually be dealing with.
I have a workaround, but still don't know what the actual problem was.
Cloning the repository into a different local tree works, and fetching data in that second tree also works. It seems the first tree was hosed in some way. I don't know if the problem was git, github, or ST. Sorry for the forum noise :(