.gitignore Generator

The Gitignore Generator creates comprehensive .gitignore files by combining templates for your project stack. Select your language(s) (Node.js, Python, Java, Go, Rust, PHP, Ruby, C#, Swift, and 90+ others), operating systems (macOS, Windows, Linux), and IDEs (VS Code, IntelliJ, Visual Studio, Xcode, Android Studio) — the tool merges canonical templates from GitHub's gitignore repository plus curated additions for modern frameworks (Next.js, React, Vue, Django, Flask, Spring Boot, etc.) into a single optimized .gitignore.

A good .gitignore keeps your repository clean by excluding: build artifacts (dist/, target/, build/), dependencies (node_modules/, venv/, vendor/), OS metadata (.DS_Store, Thumbs.db, desktop.ini), IDE configs (.idea/, .vscode/ — sometimes), logs (*.log, logs/), secrets (.env, *.pem), and build caches (.next/, .nuxt/, .cache/). Without a proper gitignore, your repository bloats with machine-specific files, IDE junk accumulates in commits, and worst — secrets leak into git history. This tool creates the right .gitignore in seconds.

.gitignore files tell Git which files to ignore in a repository. Once a file is ignored, Git will not track changes to it or include it in commits.

Syntax:

```
# Comments start with #

# Ignore specific file
secrets.txt

# Ignore all .log files
*.log

# Ignore entire directory
node_modules/

# Negation: track this even though parent pattern ignored
!important.log

# Match any level of nesting
**/logs/*.log

# Match at root only
/build

# Match all .tmp files anywhere
*.tmp
```

Pattern rules:

- * — matches anything except / (does not cross directories)
- ** — matches anything including / (crosses directories)
- ? — matches single character
- [abc] — character class
- / prefix — match only at root
- / suffix — only directories
- ! prefix — negation (re-include)
- # — comment
- Blank lines ignored

Precedence:

Later rules override earlier ones. Use ! to re-include files that would be ignored by an earlier pattern.

Global gitignore:

You can set a global .gitignore for all your repositories:

``bash
git config --global core.excludesfile ~/.gitignore_global
``

Put personal preferences in global (IDE configs, OS files). Put project-specific in project gitignore (node_modules, dist). Do not put personal files in project gitignore — contaminates teammates.

Common categories:

Language-specific:

- Node.js: node_modules/, .env*, *.log, dist/
- Python: __pycache__/, *.pyc, venv/, .pytest_cache/, *.egg-info/
- Java: target/, *.class, *.jar
- Go: vendor/, *.exe, *.test
- Rust: target/, Cargo.lock (for libraries)

OS-specific:

- macOS: .DS_Store, .AppleDouble, ._*, Icon?, Thumbs.db, ehthumbs.db
- Windows: desktop.ini, *.lnk, *.bak, $RECYCLE.BIN/
- Linux: .directory, .Trash-*, *~

IDE-specific:

- VS Code: .vscode/ (if sharing settings, commit .vscode/settings.json but ignore .vscode/*.log)
- IntelliJ: .idea/ (team-level or personal depending on team decision)
- Vim: *.swp, *.swo, tags
- Emacs: *~

Secrets and sensitive:

- *.env files (exceptions: .env.example)
- *.pem, *.key (private keys)
- credentials.json, secrets/
- *.p12, *.keystore

Build artifacts:

- dist/, build/, out/, bin/, obj/, target/
- *.exe, *.dll, *.so, *.dylib
- Coverage reports: coverage/, *.lcov

Important exceptions:

- package-lock.json, yarn.lock, Cargo.lock (applications) — include these
- *.pem.example (template) — include
- .env.example — include

Team-level decisions:

- .vscode/settings.json — commit if team shares settings, ignore if personal
- .idea/ — usually ignored, but some teams share certain files
- dist/ (for libraries) — depends if you publish from repo

Useful combinations:

A Node.js full-stack project typically needs templates for:
- Node.js (language)
- Next.js or React (framework)
- macOS (your OS)
- Windows (teammate OS)
- VS Code (IDE)

Tool-generated vs hand-written .gitignore: Tool-generated covers 95% of common cases with proven patterns. Hand-written is for specific project needs. Start with generator, customize after.

Global vs project gitignore: Global (~/.gitignore_global) is personal preferences across all your projects. Project (.gitignore in repo root) is shared with team. Keep personal out of project gitignore.

.gitignore vs .dockerignore: Similar syntax, different purposes. .gitignore: files excluded from git commits. .dockerignore: files excluded from Docker build context. Usually different content (gitignore excludes node_modules for git; dockerignore excludes it for build context too).

.gitignore vs .npmignore: .npmignore: files excluded from npm package publish. If absent, npm uses .gitignore. Usually different — .gitignore keeps tests and docs in repo; .npmignore excludes them from published package.

.gitignore vs git attributes: .gitignore excludes files. .gitattributes sets per-file attributes (eol, diff, merge). Both committed to repo.

GitHub templates vs Toptal: Both offer gitignore templates. GitHub maintains the primary canonical source at github.com/github/gitignore. Toptal has a nice UI. This tool uses GitHub templates.