git-credential-manager VS 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.)

# download a repository on GitHub to our machine # Replace `owner/repo` with the owner and name of the repository to clone git clone https://github.com/owner/repo.git # change into the `repo` directory cd repo # create a new branch to store any new changes git branch my-branch # switch to that branch (line of development) git checkout my-branch # make changes, for example, edit `file1.md` and `file2.md` using the text editor # stage the changed files git add file1.md file2.md # take a snapshot of the staging area (anything that's been added) git commit -m "my snapshot" # push changes to github git push --set-upstream origin my-branch

// https://github.com/owner/repo/blob/branch/path/to/Contract.sol import "https://github.com/owner/repo/blob/branch/path/to/Contract.sol"; // Example import ERC20.sol from openzeppelin-contract repo // https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol";

Thanks for the feedback!

w.r.t Bypass idea 1: in the future, the plan is to have application level policy, e.g. only allow 'GET https://github.com/owner/repo'.

w.r.t Bypass idea 2: in the future, the plan is to have a policy to disable sudo. Once that is done, user code will not be able to mess with the agent.

GCM Core does support multiple users with GitHub remotes. You have to put the username in the remote URL, for example:

https://[email protected]/owner/repo

GCM will store credentials for "alice" only. Repositories that have remote URLs with a different "user@" will use different credentials.

Remote URLs without a "user@" part at all (like "https://github.com/owner/repo") are treated like the "default" user for GitHub.com, rather than a specific one.