.gitignore Generator
Select every language, framework, and editor your project touches. The rules are combined into a single file with duplicate lines removed.
How to use it
- Check every stack, framework, and editor your project uses.
- Copy the output, or download it directly as
.gitignore. - Place the file in your project's root folder, next to
.git.
How it works
Each option maps to a fixed, hand-maintained list of common ignore patterns for that ecosystem. Selecting several options merges their lists and removes exact duplicate lines, keeping the file readable.
Limitations
These are common, general-purpose patterns — not a live copy of GitHub's official template collection, so highly project-specific build paths may need adding by hand.
Frequently asked questions
- Can I combine multiple stacks, like PHP and Node?
- Yes — check every option that applies to your project (for example Laravel, Node, and VS Code together) and the rules are merged into one file with duplicates removed.
- I already have a .gitignore. Can I add to it?
- Yes — copy the parts you need from the output and append them to your existing file, then remove any duplicate lines.
- Why is my .env file listed?
- Environment files usually hold secrets like API keys and database passwords, so most stack presets exclude them by default. Double-check this matches your project's setup before committing.
- What if I've already committed a file I now want ignored?
- Adding it to .gitignore only stops new changes from being tracked. For a file already committed, run `git rm --cached <file>` first, then commit that removal.