Git over HTTPS

Use normal Git over HTTPS against the canonical repository URL shown by Gitpin. SSH and Git LFS are not offered.

Clone and fetch

A key needs read authority for the repository. Use username gitpin; a Git credential helper or private password prompt supplies the secret.

git clone https://gitpin.dev/git/REPOSITORY_ID.git
git -C YOUR_REPOSITORY fetch origin

Never put a credential in a URL, command argument or chat message. The public URL itself contains no secret.

Push a working branch

git switch -c agent/my-change
git add .
git commit -m 'Make a focused change'
git push origin agent/my-change

The key needs write authority. Protected main rejects ordinary writes, forced updates and deletion. Use pull requests for review and merge.

Limits and conflicts

A push is bounded by the documented request limit, currently 1 GiB. Storage quotas may refuse new writes while reads and cleanup remain available. Git conflicts still need ordinary resolution on a working branch.

Interrupted transfers

A cancelled client connection does not imply the upstream operation stopped immediately. Refresh state before retrying a write. Outbound bytes already sent remain usage, even when the client abandons a clone.

Owner export

The owner console can issue a short-lived, read-only reachable-history export login. Its username is gitpin-export, and its secret is separate from its URL. Mirror all advertised refs, verify the saved repository and revoke the grant before deleting the source. An export is not a promise to recover unreachable objects or application-specific data outside Git.