Sourcetree had been happily auto checking the remote status of repos (as specified in Tools -> Options -> Check default remotes...) until the recent update, when it mysteriously stopped working!
I now have to manually tell Sourcetree to refresh each individual repo via the Repository -> Refresh remote status option. This is obviously quite annoying, as I have a number of interdependent projects open.
Is this a known bug in the latest release? Can I do anything to fix it? Just to be clear, the Tools -> Options -> Check default remotes option is definitely checked. Nothing has been changed in any other settings; it just stopped working of its own accord. I am using Bitbucket to host my repos.
Thanks for your help
If it helps at all, for me this is no longer an issue - one of the interim updates may have fixed it; I'm really not sure! I would suggest that everybody above make sure they have the latest Sourcetree update, although I'm sure you've all done that already...
We are using Stash and SourceTree. When branches are deleted in Stash they are not removed by the local SourceTree Windows client.
My use case:
So, to properly update I need a fetch plus a 'git remote prune origin'
Not sure I understand what SourceTree is supposed to do when one or more branches has been removed in the remote repo.
Re: Auto refresh repo setting:
A. Is the Remotes-node supposed to mirror the list of branches in the remote repo?
Re. "Prune tracking branches..." option on in the fetch-dialog:
B: Is it supposed to remove branches from the Remotes-node that no longer exist in the remote repo?
C: Is it supposed to remove branches from the Branches-node that no longer exist in the remote repo?
For me even manual action on Repository -> Refresh remote status does not work. I have couple of remore branches deleted (I'm using Stash btw) and they're still visible in SourceTree.
When I'm trying to delete remore branch using SourceTree I'm getting errror:
git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree branch -d -r origin/feature/HORST-435 Deleted remote branch origin/feature/HORST-435 (was 5632d55). git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push origin :feature/HORST-435 error: unable to delete 'feature/HORST-435': remote ref does not exist error: failed to push some refs to 'ssh://firstname.lastname@example.org:7999/platform/core.git' Completed with errors, see above
Which is quite obvious because this branch doesn't exist. But thats the only way to get rid off this stuff from my SourceTree remotes view.
Same problem here - sometimes when I commit something, THEN the view is updated. Worst case scenario I am a few commits behind and have one push pending; I need to rebase and discard all changes in order to pull.
Now i'm teaching all my colleagues to pull before committing anything..
Using sourcetree 1.6.14 and stash.
I meet this issue for several months, but at the first of time, it works fine.
I am update to new version bunch of times even to new released 2.1 in Mac OS 10.11.1.
Still can't work. I need manually click the fresh button to get all of remote branches.
But in my own Macbook, it works fine too.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs