I find that a growing list of remote repositories, which have been created by my colleagues are not automatically deleted when removed from GitHub. When I manually delete them I get an error stating that they don't exists. How can I make SourceTree automatically manage and remove these remote repos when they are removed by my peers?
That's against the principles of distributed version control system, which do not have a main/reference location for a repository by concept. It's only a convention that most of us consider github/Bitbucket as a reference location for repositories - but that's not part of the distrubuted VCS strategy of git. SourceTree implements only the concepts of git here ... so there is no automatic deletion of your repository, when the reference repository is deleted.
Assumed the following case: Your repository is hosted on github as well as on bitbucket. You might have configured both of them as remote repositories - what shall happen, if the refernce repository is deleted on github? Should it be deleted - unless you have configured a second reference repository?
Either you misunderstood my question or I misunderstood your answer. My apologies if I'm a little confused.
First of all, in the scenario you presented, I would not expect either the second remote repository or the local repository to be deleted. What I would expect is that the UI would be updated so that it was obvious to me that the remote GitHub repository no longer existed, due to deletion. This would leave my local copy and the remote copy on Bitbucket unaffected.
My issus is that I have indications that remote repositories exist when indeed they do not. I would have expected the pull command to update the tracking references thereby updating the status of remote repositories.
The issue here is really about synchronization more than manual or automatic deletion of remote references. I'm not the one deleting the remote repositories. What happens is that I and my teammates submit code for review on temporary branches. When these branches are merged, whomever performed the code review and merge then deletes said temporary branch. So, over time, I have references to these remote branches that no longer exist accumulating in my instance of SourceTree. The included image is an example of the accumulation I'm referring to. Most of these branches don't exist anymore. It would be nice if I didn't have to attempt to delete them in order to figure that out.
Screen Shot 2016-02-02 at 19.35.53.png
I believed i had the same problem. The repository had been deleted from BitBucket but the bookmark for the repository still appeared in SourceTree.
I fixed it by deleting the local repository folder on my hard-drive then once the bookmark in sourcetree said the folder had been deleted i clicked on the bookmark and selected delete bookmark.
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
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