What is a .gitignore Generator?
Every repo needs one, and the cost of a bad one is real: node_modules bloating history, .env files leaking credentials, .DS_Store noise in every diff.
Select your languages, OS and editors; get one combined file with a secrets section included by default.
Frequently asked questions
A file I ignored is still tracked: why?
.gitignore only affects untracked files. Run git rm --cached <file> to untrack something already committed.
Should .env really be ignored?
Always: commit a .env.example with variable names instead. Leaked credentials in git history are painful to purge.
Do OS templates belong in the repo or globally?
Purists put .DS_Store in a global gitignore; in practice including them in the repo protects every collaborator.
Can I edit the output?
Of course: it is a plain text starting point; add project-specific patterns freely.