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

The Git host refused to serve LFS objects because the repository (or its owner) has used up its LFS storage or bandwidth allowance. This is a billing/quota limit, not a network or auth fault.

What this error means

An actions/checkout with LFS, or git lfs pull, fails with batch response: This repository is over its data quota. The pointers are present but the content cannot be downloaded until quota is restored.

Downloading assets/model.bin (126 MB)
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 quota exhausted

Every CI run that pulls LFS content consumes bandwidth against the account quota. High-frequency pipelines burn through the monthly allowance quickly, after which downloads are blocked.

LFS storage limit reached

Large or numerous tracked binaries can exceed the storage budget. Once over, the host stops serving objects until more storage/data packs are added.

How to fix it

Reduce LFS bandwidth used by CI

1. Cache LFS objects between runs so each job does not re-download them.
2. Only fetch the LFS files a job actually needs (git lfs pull --include="path/*").
3. Skip LFS where content is not required (lfs: false for jobs that do not touch large files).

Cache LFS objects in the workflow

Persist the LFS object store keyed on the LFS file list so most runs hit the cache instead of the quota.

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

Raise the quota

If usage is legitimate, purchase additional LFS data packs (storage + bandwidth) for the account responsible for the repo.

How to prevent it

• Cache LFS objects so CI does not re-download them each run.
• Fetch only the LFS paths a job needs.
• Monitor LFS storage/bandwidth usage before it hits the limit.

Related guides