Git LFS "This repository is over its data quota" in CI

The LFS server refused the transfer because the account is over its LFS bandwidth or storage quota. This is a billing/limit condition, not a network or credential fault - retrying will not help until the quota is raised.

What this error means

A checkout or git lfs pull fails with This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs. It often appears mid-month once CI has consumed the bandwidth allowance.

git lfs output

batch response: This repository is over its data quota. Account responsible
for LFS bandwidth should purchase more data packs to restore access.
error: failed to fetch some objects from
'https://github.com/org/repo.git/info/lfs'

Common causes

LFS bandwidth allowance exhausted

Repeated CI clones each download LFS objects and count against the monthly bandwidth quota. Once exhausted, further downloads are blocked until it resets or is increased.

LFS storage limit reached

Large or numerous tracked objects can exceed the storage allowance, which also blocks access until more data packs are purchased.

How to fix it

Cut LFS bandwidth used by CI

Cache LFS objects and avoid re-downloading them on every run.

.github/workflows/ci.yml

- uses: actions/cache@v4
  with:
    path: .git/lfs
    key: lfs-${{ hashFiles('.lfs-assets-id') }}
- uses: actions/checkout@v4
  with:
    lfs: true

Raise the quota or skip unneeded objects

Purchase additional LFS data packs to lift the bandwidth/storage limit.
Use GIT_LFS_SKIP_SMUDGE=1 for jobs that do not need the binary content.
Fetch only the LFS paths a job actually uses with git lfs pull --include.

How to prevent it

Cache the LFS object store in CI to minimize repeated downloads.
Only pull the LFS paths a job needs (--include/--exclude).
Monitor LFS bandwidth usage and provision data packs before the limit.