git-credential-manager

credential helpers: like the github cli: https://cli.github.com/manual/gh_auth_setup-git or git-credential-manager: https://github.com/git-ecosystem/git-credential-manager

Also git credential manager: https://github.com/git-ecosystem/git-credential-manager

Not a fan of the namesquatting or appeal to authority or whatever you want to call the branding... Their GitHub profile (https://github.com/git-ecosystem/), with a logo anyone could mistake for the official git logo: Git Ecosystem Open source projects and tooling that support Git. Despite apparently so, AFAICT no affiliation to the git project. Turns out it's originally a Microsoft project [0]. ...So does Microsoft still manage the "github.com/git-ecosystem" org or has it been transitioned to new owners by now? [0]: https://github.com/Microsoft/git-credential-manager-core

GCM (which I guess inspired this) is already available via Homebrew https://github.com/git-ecosystem/git-credential-manager/blob...

Git has a lot of options for managing credentials ( https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage https://git-scm.com/docs/gitcredentials https://docs.github.com/en/authentication/keeping-your-accou... ). For MFA: https://github.com/GitCredentialManager/git-credential-manag... The simplest thing is to create a ~/.netrc file: machine foobar.atlassian.net login myuser1@mycompany.com password isudfiusldifuslkjhdflksjhdf machine bitbucket.org login myotheruser password kjsdoihohuaoivhdifhuvoiadhf machine github.com login companyuser1 password ghp_oisjdofhowuefoiusiofus machine github.com login personaluser2 password ghp_jf9huiehuwfsouyewuhifuh machine circleci.com login myotheruser password lkjdhiufwhu8ef7yw8yoefhozheofuhouha4lhlWiur Clone a repo

ADO works fine for me. Have you installed git-credential-manager[1]? [1]: https://github.com/GitCredentialManager/git-credential-manag...

https://github.com/GitCredentialManager/git-credential-manag... (comes bundled with Git for Windows; you can install it for macOS). SSH is also an option on both platforms, though historically a bit harder on Windows than elsewhere. (Disclosure, two of the core maintainers of GCM are GitHub employees, though GCM's goal is to work well with any Git host.)

Using username/PAT works with https://, not git://. An easier route might be GCM Core (https://github.com/microsoft/Git-Credential-Manager-Core). And of course, disclosure, I'm the product manager for GCM Core and author of this blog post.

Have you filed an issue on it? We'd be happy to investigate. https://github.com/microsoft/Git-Credential-Manager-Core/iss...

You can use a git credential manager that supports GitHub login flows. GCM Core is the big one: https://github.com/microsoft/Git-Credential-Manager-Core (It lets you login to GitHub in a popup browser window and then manages the access token for you. Stores the access token in a machine credential cache for subsequent calls on that machine.)

You can use Access Tokens which are "application specific" passwords instead of SSH keys. You can use a git credential manager such as GCM Core (https://github.com/microsoft/Git-Credential-Manager-Core) to automate the flow from username/password to access token. (It pops up a browser window where you login, retrieves and access token for you.)

You can use a supporting Git Credential Manager (such as GCM Core: https://github.com/microsoft/Git-Credential-Manager-Core) to keep using HTTPS and login/password. Instead of typing in your username/password directly in the CLI, it pops up GitHub's login page where you input login/password and then does the dance for you to get an access token from that. (Git for Windows default installs GCM Core. Some Linux distros do to. You may even already be using it. I think I've seen some confusion in comments here and elsewhere that they don't realize they are already typing in their username/password to a GCM dialog and that's going to keep working. This is about removing HTTPS Digest auth with direct password transmission over the wire.)