Add working copy and SourceTree wipes the .git folder

jeffmagill November 3, 2014

I just updated to v2.0.2 so maybe I'm just misunderstanding something. I cloned a git repo using terminal. Afterwards, I decided I wanted to work in SourceTree instead so I clicked `[ + New Repository ]` > `Add existing local repository`, found the directory and clicked ok. The repo appears in the repo list and I open it.

There is nothing there! Nothing under any of the views. Nothing when I switch to view the full branch. I try to pull but it doesn't find any remotes or branches. No history, but when I switch to the history view, I get,

> 'git log' failed with code 128:'fatal: bad revision 'master'

So I go back to terminal and type `git branch` and there are none! All my files are intact but otherwise, it looks like this is either a brand new repo, or, perhaps, a corrupted one.

I have reproduced this several times using different repositories with different remotes. Am I doing something wrong or did I stumble on a bug?

 

1 answer

1 accepted

1 vote
Answer accepted
Seth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 4, 2014

Is SourceTree set up to use "embedded" or "system" git? If it is using "embedded", but you initially cloned the repo with a newer version of git, there may be properties about the repository that causes SourceTree's older, embedded version to panic.

jeffmagill November 4, 2014

Yes. That was it. Actually, my system Git was behind at 1.7 while ST was using 1.8. This appears to have done the trick. Thanks a million!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events