On Tuesday, September 13, 2022 at 2:10:12 PM UTC+9 Matthias Koeppe wrote: > On Monday, September 12, 2022 at 8:39:50 PM UTC-7 Travis Scrimshaw wrote: > >> But people nowadays who start with GitHub never have to go through >>> archaic setup steps such as those that we document at >>> https://doc.sagemath.org/html/en/developer/trac.html#trac-authentication-through-ssh, >>> >>> which --- even when it is working --- is major friction for the project. >>> >> >> I think it has been just far too long since you uploaded your ssh key to >> GH. The server cannot magically know your ssh public key. Yes, we don't >> have https support, but other than the most casual of contributors will use >> that for push/pull. I highly doubt anyone will use that feature with any >> serious commits. >> > > You are guessing wrong. I do not use ssh with GitHub. It works perfectly > with https. >
Last I remember, using https instead of ssh meant I had to input my UN/PW every time I did a push or a pull (or maybe it gave me 5 minutes when I didn't have to do it). I always felt that was clunky and after having done that for a week, I got sick and tired of it and Googled how to store that and got to the ssh approach. I figured most other people who make regular contributions would enjoy that convenience as well. I am curious why you use https instead of ssh. Can you explain a bit? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/effa7e51-d7aa-4d65-ad4d-24a68ae15386n%40googlegroups.com.
