tos VS repo

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.

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