Git
g1t speaks git’s smart HTTP protocol. Any git client works.
Remotes
Section titled “Remotes”https://g1t.sh/<workspace>/<repo>.gitPublic repositories can be cloned without signing in:
git clone https://g1t.sh/syntaqx/g1t.gitAuthentication
Section titled “Authentication”Pushing, and reading private repositories, needs credentials. Use your username, and as the password either your account password or an access token. Tokens are recommended: they can be revoked individually and they also work for the API.
To avoid typing it each time, let git store it:
git config --global credential.helper storeCreating a repository by pushing
Section titled “Creating a repository by pushing”Pushing to a repository that does not exist, in a workspace you belong to, creates it as a public repository.
git push https://g1t.sh/<workspace>/new-repo.git mainPrivate repositories
Section titled “Private repositories”A private repository is visible only to members of its workspace. To everyone else it looks exactly like a repository that does not exist, both on the site and to git.
Branches
Section titled “Branches”Push any branch to a repository you can write to, and open a pull request from it on the repository’s Pull requests tab.
git switch -c my-changegit push origin my-changePull request forks
Section titled “Pull request forks”A pull request that was not opened from a branch has its own remote:
https://g1t.sh/pulls/<pull request id>.gitOnly whoever opened the pull request can push to it. Pushes to a fork update the pull request’s head commit on its page.
Limits
Section titled “Limits”Repositories are stored in Cloudflare Artifacts, which limits a repository to 1 GB and a single file to 32 MB. A single push is limited to 100 MB.
Git over SSH is not available yet. Use HTTPS.