By default, what is the total cache storage limit per repository for GitHub Actions dependency caching?
Select an answer to reveal the explanation.
Short Explanation
Picture one shared 10 GB closet for the whole repository. Every branch and workflow puts its caches in there, and when it fills up, GitHub clears out the ones touched least recently. You can buy a bigger closet, but 10 GB is what you get by default.
Full Explanation
GitHub Actions dependency caching limits the total size of all caches stored for a repository, and by default that limit is 10 GB. The pool is shared by every branch and workflow in the repository, so one oversized cache key can push out many smaller ones. Two eviction rules keep the pool in shape: any cache entry that has not been accessed in over seven days is removed, and when the repository reaches its storage limit, GitHub deletes caches in order of last access date, oldest first. Enterprise owners, organization owners or repository administrators can raise the limit above the default, and usage beyond 10 GB is billed to the account. The 500 MB and 5 GB figures are simply not the documented default. The no-limit option is wrong because the seven-day rule is only one eviction path; the size limit forces eviction of least recently used caches well before seven days whenever the pool is full. GitHub does not document a separate maximum size for a single cache entry, so reason about the repository total. Exam caveat: cache uploads and downloads are also rate limited per repository, so a burst of cache saves can be throttled even when storage remains. Operational check: open the repository's Actions caches page to see current usage by key and branch, and delete stale entries or narrow cache keys before raising the paid limit.