Quick answer
GitHub documents single push size as 2 GiB. The limit is enforced even when the repository itself can remain supported.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| single push sizeThe limit is enforced even when the repository itself can remain supported. | 2 GiB | Git transport | GitHubAug 22, 2026 |
Why does this limit matter?
Initial imports and history rewrites are more likely to hit the push cap than ordinary commits.
This value is scoped to Git transport; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Estimate pack size and split large migrations into verified pushes under 2 GiB.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- A single commit larger than the limit may require history rewriting rather than only smaller network batches.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related