.gitignore Generator
How to Use
- Select the languages and frameworks your project uses
- Add any custom patterns for files specific to your project
- Toggle options for comments, OS files, and IDE files
- Click "Generate .gitignore"
- Copy or download the generated file
- Save as .gitignore in your project root
Why Use a .gitignore?
- Keep repos clean - Exclude build artifacts and dependencies
- Protect secrets - Never commit .env files or API keys
- Smaller repos - Don't track node_modules or vendor folders
- Avoid conflicts - Ignore OS and IDE-specific files
- Faster Git - Less files means faster operations
- Team consistency - Everyone ignores the same files
Frequently Asked Questions
What is a .gitignore file?
A .gitignore file tells Git which files and directories to ignore in a project. This keeps your repository clean by excluding build artifacts, dependencies, logs, and sensitive files.
Where should I place the .gitignore file?
Place it in the root directory of your Git repository. You can also have .gitignore files in subdirectories for more specific rules.
Can I have multiple .gitignore files?
Yes! You can have a .gitignore in your repo root and additional ones in subdirectories. Rules in subdirectory .gitignore files apply to that directory and its children.
Why aren't my .gitignore rules working?
If files are already tracked by Git, adding them to .gitignore won't untrack them. You need to run 'git rm --cached <file>' to untrack them first.
What does ** mean in .gitignore?
Double asterisk (**) matches any number of directories. For example, '**/logs' matches 'logs' in any directory, and 'logs/**' matches everything inside logs.