# Git LFS "This repository is over its data quota" (429) in CI

> Fix Git LFS "This repository is over its data quota" / bandwidth quota errors in CI - the account exceeded its monthly LFS storage or bandwidth allowance, so batch requests return 429.

Source: https://latchkey.dev/learn/command-reference/git-lfs-over-data-quota-429-in-ci  
Updated: 2026-06-30

The LFS server rejected the fetch because the account is over its monthly storage or bandwidth allowance. GitHub returns HTTP 429 on the batch API and the checkout fails before any object downloads.

## Using this in CI

CI checkouts are shallow and detached by default, which changes the answer this command gives you. Commands that read history, branch names, or tags need the checkout configured for it.

```.github/workflows/ci.yml
- uses: actions/checkout@v4
  with:
    fetch-depth: 0   # history, tags, and git describe all need this

- run: |
    git rev-parse --is-shallow-repository   # expect false
    git rev-parse --abbrev-ref HEAD          # prints HEAD when detached
```

> `git rev-parse --abbrev-ref HEAD` returns the literal string `HEAD` on a detached checkout rather than a branch name. On GitHub Actions read `github.ref_name` instead; the git command cannot know what it was checked out for.

## FAQ

### What causes Git LFS "This repository is over its data quota" (429) in CI?

There are 2 common causes: monthly lfs bandwidth allowance is exhausted and lfs storage is over the purchased quota. Every CI run that fetches LFS objects counts against the account bandwidth.

### How do I fix Git LFS "This repository is over its data quota" (429) in CI?

There are 2 fixes depending on which cause you have: reduce how often ci fetches lfs objects and confirm and raise the quota. Work through them in order, since the first is the most common.

### What does Git LFS "This repository is over its data quota" (429) in CI actually mean?

checkout or git lfs pull fails with "This repository is over its data quota.

### How do I stop Git LFS "This repository is over its data quota" (429) in CI happening again?

Cache .git/lfs so repeated CI runs do not re-spend bandwidth. The prevention section lists 3 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt