git-credential-manager VS tos

You can still use HTTPS, just not username/password as authentication. Personally, I think using HTTPS Git Credential Manager is simpler than SSH, as GCM allows you to use GitHub OAuth in your browser to sign in.

Hi, use git Credential Manager https://github.com/git-ecosystem/git-credential-manager been using it with Github and Azure Repo. Make sure that you update your machine global git config to use it.

Download Git for Windows and choose Git Credential Manager (GCM) as credential helper on the installation steps.

This is an application indepentend from git, so best use its channels. A quick search through their Github repo found this issue: https://github.com/GitCredentialManager/git-credential-manager/issues/899

Download the GCM Deb file from here - https://github.com/GitCredentialManager/git-credential-manager/releases/download/v2.0.877/gcm-linux_amd64.2.0.877.deb

When working with external Git repositories it is best practice to use multi-factor HTTPS authentication. It is best to leave the default option by using the built in Git Credential Manager.

(We haven't started using Git Credential Manager Core yet and I haven't done any research into it, so I don't know if it'll throw a wrench in things.)

It may be meant for software developers but has legitimate value in other domains. For example, DigitalOcean has their legal team use it as a way of providing diffs on their terms of service and other policies. This type of use case is where it benefits everyone, in my opinion, to reduce the friction to get started.

https://github.com/digitalocean/tos

There are plenty of text file versioning use cases I think, from configuration files for system administrators to LaTeX papers for science students who could benefit and should have an easy path to using it.