Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean GitHub has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for GitHub. The baseline covers recommended on-disk repository size, regular Git file size, single push size, maximum Git LFS object. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| 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 |
| regular Git file sizeFiles beyond the hard block require Git LFS or an external release/storage path. | 50 MiB warning; 100 MiB hard block; 25 MiB browser upload | Regular repositories | GitHubAug 22, 2026 |
| single push sizeThe limit is enforced even when the repository itself can remain supported. | 2 GiB | Git transport | GitHubAug 22, 2026 |
| maximum Git LFS objectStorage and download bandwidth are metered separately from the per-file ceiling. | Free/Pro: 2 GB; Team: 4 GB; Enterprise Cloud: 5 GB | Git LFS | GitHubAug 22, 2026 |
Tracked constraints and impact
Repository, object, push, browser upload, diff, and Git LFS limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
GitHub Repository Size Limits
GitHub Repository Size Limits, verified against GitHub's official documentation with scope, implementation impact, caveats, and a direct check.
GitHub File Size Limits
GitHub File Size Limits, verified against GitHub's official documentation with scope, implementation impact, caveats, and a direct check.
GitHub Push Size Limit
GitHub Push Size Limit, verified against GitHub's official documentation with scope, implementation impact, caveats, and a direct check.
GitHub Git LFS File Limits by Plan
GitHub Git LFS File Limits by Plan, verified against GitHub's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current GitHub baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Repository, push, object, diff, branch, and activity limits
Browser, warning, block, and repository sizing limits
Plan-specific per-file limits