Skipping .. since it's not initialized?

[mdeguzis]

I am parsing the readme, but only saw this PR: #11. What is the criteria here? Why won't the repos clone? They are definitely there an we use them everyday with active code.

Skipping name (git@github.com:ORG/name.git) since it's not initialized

I know it exists fine:

$ git ls-remote https://github.com/ORG/name.git
Username for 'https://github.com': name
Password for 'https://name@github.com':
<hash>        HEAD
<hash>refs/heads/master
<hash>refs/remotes/origin/HEAD
<hash>refs/remotes/origin/master

[mdeguzis]

Ok this is due to the ssh key of the user initiating the command not existing. I'll see if I can fix this and submit a PR. Also, the 404 not found needs to note which item is 404, it is just plain confusing to see that, and think that your code is not being cloned, when infact is just one of the items not being pulled due to not found.

[josegonzalez]

@mdeguzis pull requests welcome. This project does what I need, so I'm unlikely to fix these things myself, but am happy to pull in fixes/changes others need.

[einsteinx2]

Ran into this same confusion the other day when I first used this tool. In my case, I see this message any time a repo does not have a wiki (as the wiki git repo is not initialized). About to file and issue for and fix another issue, but after that I'll take a crack at handling that case better and submit a PR. Was very confusing the first time I ran it when I thought most of my repos were not being backed up when it was just the wikis which don't actually exist (so aren't actually an error).