About this tool
A good .gitignore keeps build output, dependencies, secrets and OS cruft out of your repository from the very first commit. Tick the languages, frameworks and editors your project uses and this tool stitches the matching sections together, removing duplicate lines so the result stays tidy.
The templates are condensed from the official github/gitignore collection and bundled into the page, so nothing is fetched from a server. Copy the result or download it straight as .gitignore.
Frequently asked questions
What does a .gitignore file actually do?
It tells Git which files and folders to leave untracked — build output, dependencies like node_modules, OS files, IDE settings, secrets — so they never get staged or committed by accident.
Can I combine templates for multiple stacks, like Node plus macOS plus VS Code?
Yes. Check as many templates as you need and they're merged into one file, with duplicate rules removed automatically so the result stays clean.
I added a .gitignore, but Git is still tracking a file it should ignore — why?
A .gitignore only affects files Git doesn't already track. For a file that was committed before you ignored it, run `git rm --cached <file>` to untrack it, then commit — the ignore rule takes effect from there on.
Where do I put the generated file?
Usually in your repository root, alongside .git. You can also add nested .gitignore files in subfolders for rules that should only apply there.
Does the tool remember which templates I picked?
Yes. Your selections are saved in your browser so they're already checked next time you open the tool.