Limits

Limits keep requests predictable and shared capacity usable. Current defaults come from the service configuration; a deployment may lower them.

Git and storage

A single Git push is capped at 1 GiB. An organisation also has a soft physical-storage quota. Unlimited repository count is not a promise of unlimited push size or capacity. Above quota, new writes can be refused while reads and cleanup remain available.

Bounded responses

Lists use bounded pages and opaque cursors. Content, files and diffs have response limits. A binary or oversized file may show metadata and an explanation instead of rendered content. The UI must not treat a truncated response as a complete file.

Authority

Every key has a required expiry. Children can only narrow their parent's authority. Protected main is not a normal write destination. Cross-organisation IDs do not reveal private resource identity.

Unavailable interfaces

There is no SSH transport, Git LFS, hosted CI runner, issue tracker, wiki UI, code search or customer webhook service. The client repository has no released Gitpin CLI. Check the current availability index before choosing an integration.