Changed GitHub URLs from SSH to HTTPS #97
Conversation
In general, GitHub seems to prefer HTTPS over SSH, and they provide good support to use it for read-only and read-write repositories on their site. In general, HTTPS is more fool-proof than SSH. In this commit I've replaced our root-level advice on cloning repositories with HTTPS URLs.
|
@gvwilson AFAIK when using HTTPS you always have to enter your username and password. |
|
@gvwilson @r-gaia-cs - The mechanics are somewhat different, but the answer is yes. I should have originally linked to the GitHub's Set Up Git, where they describe how to set things up for HTTPS. |
|
+1 as this tends to be easier for beginners. No need to setup SSH keys. |
|
@ahmadia To you mind add a box to talk about "Password caching" or a link to GitHub's Set Up page? It request git >= 1.7.10 that shouldn't be a problem since msysgit and Debian Wheezy already use this version or a new one. Otherwise this have green light to merge. |
|
Let's get this merged :) |
Changed GitHub URLs from SSH to HTTPS
|
On Wed, Oct 23, 2013 at 02:09:34PM -0700, Will Trimble wrote:
So I'm a few hours too late, but in my current attempt to split the |
|
On Wed, Oct 23, 2013 at 07:24:31PM -0700, W. Trevor King wrote:
Although I see this is ssh:// to https:// ;). Sorry for the noise :p. |
In general, GitHub seems to prefer HTTPS over SSH, and they provide good
support to use it for read-only and read-write repositories on their
site. In general, HTTPS is more fool-proof than SSH. In this commit
I've replaced our root-level advice on cloning repositories with HTTPS
URLs.