11

Git newbie here. I'm setting up git on a new Ubuntu VM and trying to clone some repos. The clone works for the following command:

git clone http://github.com/organisation_name/repo_name

(after prompt for username/password), but fails for 

git clone git://github.com/organisation_name/repo_name

and also 

git clone git://github.com/organisation_name/repo_name.git

with the same error message:

Cloning into 'repo_name'...
fatal: remote error:
Repository not found

Of course the obvious answer is "use the http method", but I'm trying to understand why one works and the other doesn't. Any suggestions? (also is there any difference when using the .git extension on the repo name btw?)

Thanks!

4

4 回答 4

10

Well, I think you are using the wrong url in your second case

Try this instead 

git clone git@github.com:organisation_name/repo_name.git

The difference is the : in the url when using git@ vs the / you are currently using, and the extra .git at the end.

This should be the same url if you go to github and select the ssh url for cloning (and not the https one selected by default)

于 2013-10-30T13:40:22.240 回答
7

If this is a private repository, you need to add your machine's ssh public key to you account under https://github.com/settings/ssh otherwise you will get the exact error you are listing here.

于 2013-10-30T13:33:37.280 回答
1

I just wanted to throw out there that my problem was the network. All of my settings were good. I was told the network didn't filter or block ports or anything, but after trying everything I could think of and everything I could find online; I finally tethered my laptop to my mobile phone and everything started working just fine.

于 2014-10-08T20:07:27.643 回答
1

Query: why HTTPS URL works and SSH URL doesn't?
The purpose of SSH URLs is to provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the public key to your GitHub account.

于 2018-01-09T10:44:35.793 回答