repo VS git-credential-manager

The button on the browser just navigates to the URL `git-peek://https://github.com/name/repo`. How your system handles this git-peek protocol is completely up to you. While the git-peek package does offer to setup a handler for this custom git-peek protocol, I went ahead and set it up manually. Now, my system calls this bash script whenever it encounters the git-peek protocol:

  #!/usr/bin/env bash

You just clone the repository onto that computer with git clone https://github.com/name/repo. It should work automatically

I have a /home/.ssh/ directory, with id_rsa and id_rsa.pub inside, and I think that's the reason i don't have to manually authenticate, however every post i found about how to use this method also explains that i have to associate the key with my account or repo on github, which i haven't done (at least, when i go to my github setting there's aren't any SSH keys registered), and to use SSH-compatible URLs for my repos, which i'm not doing neither (i'm just using the very normal https ones, like https://github.com/name/repo).

you can install a package with git like using pip install git+https://github.com/name/repo

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.)