ToolHub
๐Ÿšซ

.gitignore Generator

Combine .gitignore templates for your stack.

Pick stacks & environments

.gitignore
# Node
node_modules/
dist/
build/
coverage/
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.env
.env.*
!.env.example
.DS_Store

# macOS
.DS_Store
.AppleDouble
.LSOverride
Icon?
._*
.Spotlight-V100
.Trashes
*.icloud

# VSCode
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
history/

About the .gitignore Generator

Assemble a .gitignore from fourteen curated templates covering language stacks like Node, Python, Rust, Go and Java, frameworks such as React / Vite and Docker, plus OS and editor noise from macOS, Windows, Linux, VSCode, JetBrains and Xcode. Each selected template lands as a labeled section in one merged file ready to download.

How to use the .gitignore Generator

  1. Tick every stack your project uses โ€” for example Node, macOS and VSCode.
  2. Review the merged .gitignore output with its per-template comment headers.
  3. Add or remove templates until the list covers your toolchain.
  4. Use the download button to save the file into your repository root.

.gitignore Generator FAQ

Which templates are included?

Fourteen: Node, React / Vite, Python, Rust, Go, Java, Docker, macOS, Windows, Linux, VSCode, JetBrains, Xcode / Swift โ€” each with the standard artifacts, caches and .env entries for that stack.

Can I combine language and editor templates?

That is the intended workflow โ€” the default selection is Node, macOS and VSCode, and any combination merges into one file with a comment separating each section.

Does it keep .env.example visible while ignoring .env?

Yes. The Node template ignores .env and .env.* but includes the !.env.example negation so your example file stays tracked in git.