> For the complete documentation index, see [llms.txt](https://docs.lingoql.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lingoql.com/introduction/troubleshooting-deploys/github-cloning-limits.md).

# GitHub cloning limits

LingoQL applies these repository limits when cloning from GitHub:

* `1GB` maximum repository size
* `50MB` maximum per file

If either limit is exceeded, cloning can fail before the build starts.

### What counts against the limit

Large repositories usually include one of these:

* committed build output
* videos, archives, binaries, or datasets
* large images or static media

A single file above `50MB` is enough to block the deploy.

### Recommended fix

Store large static assets in object storage.

Then reference those assets by URL from your app.

This keeps deploys smaller, faster, and easier to update.

### Good patterns

* keep source code in Git
* keep large media in object storage
* fetch or reference large files at runtime by URL

### What to remove from the repo

Remove files that do not need to be cloned for every deploy.

Typical candidates:

* generated bundles
* exported media
* model weights or large seed data
* local caches and dependency folders

### Check your repo locally

Use a few quick checks before you push:

```bash
find . -type f -size +50M
```

```bash
git count-objects -vH
```

```bash
du -sh .
```

These checks help you catch large files and an oversized repository early.

### Quick recovery checklist

1. Remove files above `50MB`.
2. Keep the full repo under `1GB`.
3. Move large static assets to object storage.
4. Reference those assets by URL from the app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lingoql.com/introduction/troubleshooting-deploys/github-cloning-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.