.gitignore Generator
Build a clean .gitignore for any stack — languages, frameworks, editors and OS.
Runs entirely in your browser.
Your data never leaves this device and is never sent to our servers.
Nothing selected yet
.gitignore
Committing node_modules, a .env file or an editor folder is the kind of mistake that is annoying at best and a security incident at worst. Pick the templates matching your stack and get a combined, commented .gitignore.
A secret that has already been committed is not removed by adding it here — it stays in history and must be rotated.
How to use it
- Select the languages, frameworks, editors and operating systems you use.
- Review the combined output.
- Copy it into a .gitignore at the root of your repository.
Not working as you expect? Report a problem with this tool.
Frequently asked questions
I already committed a file — will this remove it?
No. .gitignore only affects untracked files. Run git rm --cached on the file, then commit. If it was a credential, rotate it: it remains in history.
Where should the file live?
At the repository root for project-wide rules. Subdirectories can have their own .gitignore for local rules.
Does the order of entries matter?
Yes for negations. A ! rule that re-includes a file must come after the pattern that excluded it.