From: Julia Evans Date: Mon, 26 Oct 2026 20:03:25 GMT Subject: Re: [PATCH 2/2] doc: add new Git tutorial for beginners Message-ID: <8e2a3ad0-2d04-409b-ab1f-17553cf2dce9@app.fastmail.com> In-Reply-To: >> I'm sure I've read somewhere that ssh is a nightmare to set up on >> Windows, so a first-class mention of it may put off Windows users. It >> might perhaps get a note that it's for Linux/Unix/etc users only (or >> only-ish). Anyway, I've been developing on Windows for about 30 years >> and using Git for about eight, and never needed ssh for anything. >> Https is all that I've used for GitHub and BitBucket, which you might >> consider likely to be the most common servers users might see. And >> bearing in mind that GitHub has on-prem versions that may be found in >> corporate settings. I'm not sure how easy it is to set up a local Git >> server by other means as I've never really tried. > > I think the idea of giving HTTPS instructions is interesting. > I don't know if it's possible to give vendor-neutral directions for how to set > up Git with HTTPS, but if it is I'd be happy to give it a try. I'd love any > pointers or suggestions for how to do this. I just did some research and I found out that Git for Windows comes with Git Credential Manager, which pops up a little dialog the first time you run `git push` asking you to log in to your Git host. It looks like it works on most popular Git hosting services, and if anybody is running their own Git server that only works with SSH auth then they can follow the SSH directions. So I think that we can separate the authentication setup into the Windows section (where we tell people to use GCM) and the Mac/Linux section (where we tell people to use SSH).