[python-committers] New workflow - some questions

Paul Moore p.f.moore at gmail.com
Sat Jul 29 09:30:39 EDT 2017

On 29 July 2017 at 14:13, Nick Coghlan <ncoghlan at gmail.com> wrote:
> To be honest, the read-only=HTTPS & read/write=SSH split is likely a
> Linux+macOS-ism, where we can do "ssh-add" once, and then never have
> to worry about explicitly authenticating again until we reboot our
> client machine. As Inada-san notes, the password prompt when
> accidentally doing a direct push to a HTTPS clone then serves as a
> reminder that you probably meant to push to a different remote that's
> set up for read/write access over SSH.
> There's no functional difference on the server side though - it's
> strictly about how the git client authenticates your identity with the
> server.

On Windows you can use the git credential manager to store credentials
in the OS cert store, and then https is passwordless for push.


More information about the python-committers mailing list