Documentation
Git access
Clone, fetch, and push over HTTPS. Use SSH when it appears in a repository's Clone menu.
Upstream uses standard Git transport. You can use ordinary Git clients, IDEs, and CI systems without a custom protocol.
HTTPS remote
https://git.coline.app/{namespace}/{repository}.git
Public repositories allow anonymous clone and fetch. All pushes and all access to private repositories require authentication. An unclaimed repository comes with a push URL that carries its own credential.
HTTPS credentials
Create a repository-scoped credential in Git settings. The secret is shown once and stored only as a hash.
When Git prompts:
- Username: any non-empty value
- Password: the complete
col_git_...credential
Credentials can be read-only or read/write, expire automatically, and can be revoked from settings.
SSH
When SSH appears in a repository's Clone menu, add a public key in SSH key settings and use the SSH URL shown there:
git@ssh.git.coline.app:{namespace}/{repository}.git
Automation
Repository administrators can issue a read-only automation credential for a build or deployment service. Scope it to one repository, give it a clear actor name, and revoke or rotate it when the integration changes.
Size limits
| Limit | |
|---|---|
One push with git push over HTTPS | 5 GB |
One push with upstream push or over SSH | None set. A push needs room in Upstream's storage while it is received. |
| Repository | None |
| One file in Git history | 256 MB. Track larger files with Git LFS. |
| Git LFS object | 5 GiB each |
| Unclaimed repository | 100 MiB in all |
For anything larger, use upstream push with the same arguments you'd give git push (CLI 0.7.1 or newer), for example upstream push -u origin main. It runs Git's own push, sent straight to Upstream's storage. Clones and fetches have no size limit.