Does it exclude .env files containing secrets?
Yes, standard environment patterns (.env, .env.local, .env.*.local) are included by default to prevent accidental credential leaks.
Generators
Generate focused .gitignore rules for common stacks.
Add an input and run this tool to see the output.
Run AIOptional, bring your own key.
Add your own AI provider in AI settings to enable AI help for this tool. Nothing is sent until a key is configured.
Gitignore Generator Developer Guide
100% Client-Side & PrivateCombine practical ignore rules for Node, Next.js, VS Code, operating systems, and environment files into one local .gitignore.
Key capabilities
- Combines proven .gitignore ignore rules for common stacks (Node.js, Next.js, Python, macOS, Windows, VS Code)
- Automatically deduplicates conflicting or overlapping ignore patterns
- Includes helpful category comments and standard environment file exclusions
- One-click file download or clipboard copy
Common use cases
- Bootstrapping new repositories with complete, secure ignore patterns
- Preventing sensitive .env files, build artifacts, and OS temp files from being committed
- Updating legacy projects with modern framework-specific ignore rules
How to use Gitignore Generator
- Select your technologies and operating systems from the template list
- Review the combined and deduplicated .gitignore output in the preview panel
- Copy the text or save it directly as `.gitignore` in your repository root