Quick answer
GitHub documents recommended on-disk repository size as 10 GB recommended maximum. On-disk size refers to the compressed .git directory and is a repository-health guideline.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| recommended on-disk repository sizeOn-disk size refers to the compressed .git directory and is a repository-health guideline. | 10 GB recommended maximum | GitHub repositories | GitHubAug 22, 2026 |
Why does this limit matter?
Large history slows clones, fetches, CI, maintenance, and browser operations.
This value is scoped to GitHub repositories; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure the .git directory, largest objects, generated content, and clone time.
- 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
- GitHub can consider interacting health factors beyond raw repository bytes.
- 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