Vovy removes the oversized file from your unpushed commits, moves big assets to Git LFS or storage, and gets your push through.
GitHub rejected my push because a video file is over 100 MB, fix it
How it works
- Read the rejection: Vovy reads the GH001 Large files detected error and finds exactly which file and which commit tripped it.
- Decide where it belongs: A card compares options: Git LFS for files the code needs, a storage bucket for user media, or ignoring build outputs.
- Remove it from history: The file is in a commit, so deleting it now is not enough. Vovy rewrites only your unpushed commits to drop it.
- Move it somewhere better: Vovy sets up Git LFS for that file type, or uploads it to a Supabase Storage bucket and links it from your code.
- Push successfully: Vovy pushes, confirms GitHub accepts it, and adds the pattern to .gitignore so it cannot happen again.
What you provide
- The repo with the failed push
- Where you want big files to live
What you get
- Your push going through
- The big file stored properly
- Clean history
- A rule to prevent a repeat
FAQ
What are GitHub's size limits?
GitHub blocks files over 100 MB and warns above 50 MB. Repos should ideally stay under 1 GB.
Why can't I just delete the file and push again?
The file still exists in an earlier commit you are trying to push. It must be removed from those commits.
Is Git LFS free?
GitHub includes a small free LFS storage and bandwidth allowance. Heavy use needs a paid data pack.
Related tasks
All tasks