Limits
Technical and preview limits
Planned account allowances are not current deployment limits. Preview capacity and technical ceilings remain separate from pricing, and unlimited repository count does not mean unlimited storage or execution.
The previously published fixed preview storage figures are under reconciliation. Confirm effective file, push, LFS, repository and rate limits before a large import. This page does not change runtime enforcement.
| Resource | How limits apply |
|---|---|
| Git repository data | Repository count is not a storage allowance. Effective per-repository admission and service ceilings depend on the preview deployment and are being reconciled before launch. |
| Git LFS | Large-file storage and download transfer have separate planned account pools. Per-object and upload transport limits also apply. |
| Private artifacts and Packages | These share a planned storage pool. Do not count each displayed pool twice. |
| Actions caches | Cache capacity is a separate resource. Per-repository cache limits do not create an unlimited account storage entitlement. |
| Hosted workspace disks | Persistent disks are separate from Git and LFS storage. Charges may continue while a machine is stopped; pricing and retention must be confirmed before purchase. |
| Execution and abuse protection | Concurrency, job duration, network and admission controls apply independently of the advertised compute pool. Public and untrusted execution requires a qualified isolated runner service. |
See planned account allowances and ask about preview limits. Paid usage requires a disclosed rate and an explicit spending authorization; a billing-page change cannot raise an enforced limit.