Quick answer

Fix GitHub push failures caused by huge ZIPs, PDFs, videos, build folders, cache files, and accidental large commits from Termux.

Use this page when the problem matches Large File Push, not as a general reinstall guide.

For Large File Push, focus on GitHub and Git workflow and use the output to decide the next small fix instead of reinstalling everything.

What to check

Copyable command

For Large File Push, replace placeholders only when they appear in the command.

find . -type f -size +50M -print
du -sh * .[^.]* 2>/dev/null
printf "\n*.zip\nnode_modules/\n__pycache__/\n" >> .gitignore
git status

Read the output

  1. find . -type f -size +50M -print — checks the part of the GitHub and Git workflow workflow that usually causes this issue for Large File Push.
  2. du -sh * .[^.]* 2>/dev/null — shows storage usage so you know whether the device is full for Large File Push.
  3. printf "\n*.zip\nnode_modules/\n__pycache__/\n" >> .gitignore — checks the part of the GitHub and Git workflow workflow that usually causes this issue for Large File Push.
  4. git status — shows the current branch and whether files are staged, changed, or untracked for Large File Push.

Fix in a safe order

  1. Change one thing at a time while testing Large File Push.
  2. If the Large File Push error changes, read the new clue instead of repeating the old fix.
  3. Keep screenshots or copied terminal text for Large File Push; they make paid help faster if you need it.

Common mistakes

Guide did not solve it?

If large file push GitHub still blocks the upload or clone, use the Store and send the command, the branch name, and the full terminal output.

Open Store / Get Help

Related Assistance pages