aha, that wasn't previously the case, thanks for the correction
whether i'm logged in in my browser has nothing to do with whether my ssh client has access to an authorized private key
whether i'm logged in in my browser has nothing to do with whether my ssh client has access to an authorized private key
Long ago they used to push SSH as the "right" way to pull repositories (I still almost exclusively use SSH), but their change to recommending HTTPS instead by default is by now quite old: it's been the case for many years.
Other related things have changed more recently: Github doesn't allow git:// urls anymore (but HTTPS still allows anonymous checkouts), and when doing authenticated HTTPS, you now need to provide a token instead of your password.
The git:// protocol, to my recollection, doesn't support authentication at all. If you've ever been able to push to git:// URLs on Github, it's news to me.
but it seems like my original comment was incorrect in a couple of different important ways, and i appreciate people having pointed that out
Clearly, more people were confused by the original than outraged about the current implementation... I don't even recall the change being made.
https://web.archive.org/web/20180115003453/https://github.co...