Large File Push

Use This Guide When

Before You Run Anything

• Run `git status`, `git branch --show-current`, and `git remote -v` inside the intended repository.
• Back up uncommitted files before rebasing, amending, resetting, or rewriting history.
• Remove tokens, private keys, and personal paths from any output you share.

Diagnostic Or Setup Commands

Adding a path to `.gitignore` does not remove a committed file. Older commits need a verified backup and history cleanup such as `git filter-repo`, or Git LFS/Releases.

find . -type f -size +50M -print
git status --short
git log --stat -n 3
# For a file in the latest unpushed commit:
git rm --cached "PATH/TO/LARGE_FILE"
git commit --amend --no-edit

What The Commands Tell You

• `find . -type f -size +50M -print` — Searches paths by name, size, or type.
• `git status --short` — Shows the branch, staged files, conflicts, and local changes.
• `git rm --cached "PATH/TO/LARGE_FILE"` — Stops tracking a path while preserving the local file.

What Success Looks Like

• `git status` shows the expected branch and no unresolved conflicts.
• The configured remote points to the intended repository and authentication succeeds without exposing credentials.
• The pushed commit contains only the files you expected.

Safe Next Steps

1. Confirm the repository, branch, remote, and working-tree state.
2. Use the least destructive action that addresses the exact Git message.
3. Review the diff and staged files before committing or pushing.
4. Verify the result on GitHub after the push completes.

Common Mistakes

• Running Git commands one folder above or below the intended repository.
• Using force push, reset, or history rewriting before creating a verified backup.
• Putting access tokens directly into commands, screenshots, README files, or public logs.