.gitignore Generator

The .gitignore file should be placed in the root directory of your Git repository. Git applies ignore rules from the top down, so patterns in the root .gitignore affect the entire repository. You can also have .gitignore files in subdirectories for directory-specific rules.

Yes! This generator allows you to select multiple templates and combine them into a single .gitignore file. It automatically deduplicates patterns, so if Node.js and React both ignore node_modules/, it will only appear once in your generated file.

Common patterns to always include are: environment files (.env, .env.local), dependency directories (node_modules/, vendor/), build outputs (dist/, build/), IDE settings (.idea/, .vscode/), and OS files (.DS_Store, Thumbs.db). This generator includes all these in the appropriate templates.

Adding a file to .gitignore only prevents Git from tracking new files. To stop tracking files that are already in the repository, run: git rm --cached to remove it from the index while keeping it in your working directory, then commit the change.

A local .gitignore in your repository affects that project only and is shared with all contributors. A global .gitignore (configured via git config --global core.excludesfile) applies to all repositories on your machine and is personal to you—useful for IDE-specific files.

Negation patterns start with ! and re-include files that were previously ignored. For example, if you ignore *.log but want to track important.log, add !important.log after *.log. Note: you cannot negate a file inside an ignored directory.

Common issues include: the file is already tracked (use git rm --cached), the pattern has a typo or wrong syntax, the pattern is in the wrong location, or there is whitespace issues. Use git check-ignore -v to debug which rule is affecting a specific file.