Kubernetes Manifest Studio
Generate Deployment, Service, and Ingress YAML with a drift checklist.
OpenFlag the paths in a file list that probably should not be committed.
Run git ls-files or git status and copy the output.
Each path is checked against risky extensions and folders.
Flagged lines are archives, media, binaries or dependency folders.
Ignore them, move them to LFS, or keep them on purpose.
Cloning the repository suddenly takes minutes, and someone suspects a video or build artifact slipped into a commit. Before digging through history, scan the list of tracked or staged paths for the usual suspects.
Paste paths one per line, for example the output of git ls-files or git status --porcelain. Each line gets a warning marker if it ends in .zip, .mp4, .mov, .psd, .iso, .dmg, .exe, .wasm or .bin, or if the path contains node_modules or .git/. Everything else gets a neutral dot, and the report updates as you paste.
The check goes by name only. It never sees file sizes, so a 2 GB .tar.gz or a huge .csv is not flagged while a tiny test .zip is. For real sizes, git ls-tree -r -l HEAD lists blob sizes in the current commit, and git count-objects -vH reports the overall pack size. Files that are both flagged and genuinely large are candidates for Git LFS or an artifact store. Deleting a big file in a new commit does not shrink the repository, because it stays in history until you rewrite it.
Paths are checked in the browser and not uploaded. Add patterns for what you find with the stack-based .gitignore builder, and paste config files into the credential scanner while you are cleaning up.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The detector only looks at extensions and folder names, not sizes. CSV, tar.gz and many other formats are not in its list. Check actual sizes with git ls-tree -r -l HEAD.
No. The working tree gets smaller, but the file remains in history, so every clone still downloads it. Removing it for good means rewriting history with a tool such as git filter-repo, which changes commit hashes and requires collaborators to re-clone or reset.
No. A small .zip test fixture or a deliberately committed installer may be fine. The flag is a prompt to check, not a rule.