Git Ignore Simulator
Free toolPaste your .gitignore and a list of paths (or pick a local folder: only file path names are read, never file contents). For each path you'll see whether it's ignored and the exact line that decides it, with negations ("!") resolved correctly. Everything is processed in your browser: nothing is uploaded to RA Software Apps servers.
Only the file paths inside the folder are read, never their contents.
Results
| Path | Status | Rule |
|---|
Report
Markdown report
How to use it
- Paste your .gitignore.
- Type the paths to check, one per line, or pick a local folder to load its file names.
- See which paths end up ignored and which exact line of the .gitignore decides it.
What it works out and how
The simulator evaluates each path against the patterns in the same order Git does: the last matching rule wins, and negations with ! re-include what an earlier rule excluded. When you pick a folder, only the paths are read, never the file contents.
Frequently asked questions
Why does Git keep tracking a file I added to .gitignore?
Because it was already in the repository. A .gitignore only affects untracked files; to stop tracking one you have to remove it from the index with git rm --cached.
Why is my ! negation not working?
Git cannot re-include a file if its parent folder is excluded. Exclude the contents of the folder, not the folder itself, and then negate the specific path.
What is the difference between /build and build/?
The leading slash anchors the pattern to the folder of the .gitignore; the trailing slash makes it match directories only.