• Community
  • Questions
  • Why isn't my folder recognized as a valid git working copy in Sourcetree?

Why isn't my folder recognized as a valid git working copy in Sourcetree?

I found a similar question from 2013 with no answers: https://answers.atlassian.com/questions/197337/sourcetree-doesn-t-recognize-an-existing-repository

Product: Sourcetree

I'm using Windows 8 with Sourcetree 1.5.2.0

I have a valid git working copy on my local hard drive. If I go to the command-line and run "git status" from within the working directory, it returns:

"Your branch is up-to-date with oprigin/master. Nothing to commit, working directory clean"

The working directory has a valid .git folder.

The problem:

When I try to add this working directory to sourcetree, I get an error saying it isn't a valid working directory. I've tried two ways:

1. File > Open > Select Directory

Error: the path 'somepath/workingdir' is not a valid Git repository working copy.

2. Push the Clone/New button. Select the "Add Working Copy" tab. Select the correct working copy path.

Repository Type: This is not a valid working copy path.

Is this a bug or am I missing something? Thanks.

2 answers

1 accepted

15 votes

The problem was that for some reason Git support had been disabled in sourcetree. I went to the Git tab under Options and clicked "enable git support" and all is working now.

Thanks.

I had exactly the same problem.  No idea why Git Support had been disabled.  Maybe an upgrade broke it. (Using version 1.7.0.32509)

Thanks a lot for your answer, I had exactly the same problem after apply 1.10.18.1 update

0 votes
syntap I'm New Here Feb 09, 2015

I just installed SourceTree 1.6.13.0 and ran into this issue opening a copy of a repository on a travel machine.  It worked after I filled in my name/email default user info in Tools -> Options -> General tab.  I believe it asked for similar info during installation but it didn't populate that tab with it.

I also have "Allow SourceTree to modify your global Git and Mercurial config files" checked, which I'm assuming is also checked on the machine this repo was copied from.

Suggest an answer

Log in or Register to answer

Stay in touch

Be the first to know what's trending on Atlassian Community