On Mon, Dec 2, 2019 at 4:18 PM Matt Sicker <boa...@gmail.com> wrote: > > You need to configure an SSH key to use the g...@github.com URL.
Which is what I have done. Now how to you do password-prompt-less https? - Sam Ruby > On Sun, 1 Dec 2019 at 13:11, sebb <seb...@gmail.com> wrote: > > > > On Sun, 1 Dec 2019 at 16:17, Sam Ruby <ru...@intertwingly.net> wrote: > > > > > On Sun, Dec 1, 2019 at 8:30 AM sebb <seb...@gmail.com> wrote: > > > > > > > > $ git clone g...@github.com:apache/whimsy.git > > > > > > > > Cloning into 'whimsy'... > > > > > > > > Warning: Permanently added the RSA host key for IP address > > > > '140.82.118.4' > > > > to the list of known hosts. > > > > > > > > g...@github.com: Permission denied (publickey). > > > > > > > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > > > and the repository exists. > > > > > > > > Is it ever needed, or can it be dropped in favour of the alternative? > > > i.e. > > > > > > > > $ git clone https://github.com/apache/whimsy.git > > > > > > When I do a git clone with the git@github url, I can do a push without > > > specifying my password. When I do it with the https: url, I have to > > > specify my password. > > > > > > > > I can do git push with https://github.com/apache/whimsy.git; it does not > > prompt for password. > > > > I guess we have got our Gits configured differently? > > > > > > > I'm not sure what to recommend. Perhaps list both and let the user > > > choose? > > > > > > > > Seems like both are needed, so yes. > > > > > > > - Sam Ruby > > > > > > > -- > Matt Sicker <boa...@gmail.com>
