Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Cloning stuck on checking source

I'm using sourcetree and I plan to clone a repository from our github but my sourcetree got stuck on "checking source" I wonder whats the problem and how could I resolve it. I already tried using the embedded git but still it does not work

like image 654
bleyk Avatar asked Dec 02 '15 05:12

bleyk


People also ask

Why is cloning taking so long?

Part 3: Why Does Cloning Process Take So Long? Cloning your disk requires not only the right software but also that all your hardware and your operating system are in good condition; otherwise, this procedure will take longer than it should.

Why git clone is not working?

If you have a problem cloning a repository, or using it once it has been created, check the following: Ensure that the user has gone through initial GitCentric login and has the correct username, email, and ssh. This should return a usage message that refers to the config-branch, config-repo, and ls-repo commands.

Can you see how many times a repo has been cloned?

Cloning is a read-only operation, the original repository isn't modified. There is no way you can pull statistics for data that simply isn't tracked.

Why is git clone not copying source files to my local directory?

You might discover that the source files were there before, but were removed in a subsequent commit. If so, just git checkout to an older commit. Also possible that there's simply no files in the master branch ( git log --all will show other branches). See git branch for list and git checkout another branch.


1 Answers

Looks like no one was able to help with this issue. I found that getting stuck on "checking source" generally means an issue with your Git client. This can boil down to a few things.

  1. Basic configuration
    Are you using system/pre-existing Git, and it was removed or configured incorrectly? You may need to fix this, or switch to the "embedded Git" that SourceTree can install.
  2. Credential failure
    Double-check to make sure all of your credentials are correct (or delete them entirely to re-enter). SourceTree keeps authentication information in Tools > Options > Authentication.
  3. SSH keys/client configuration
    By default you'll find SourceTree attempting to communicate via SSH, this may or may not work with some hosts, if you do not have them trusted or "known". You can test getting around this by using HTTP(S) to clone your repository.

SourceTree doesn't make it very easy to observe when issues arise like this, just the ominous "checking source" that I was plagued with as well. If you haven't already figured it out or nuked it from orbit, hopefully this helps!

like image 56
nthieling Avatar answered Sep 16 '22 14:09

nthieling