ToolBark
Developer

Gitignore Generator

Build the perfect .gitignore in seconds — pick your stacks, copy, done.

Select Stacks

6 selected

Languages & Runtimes

Frameworks

Build Tools

Editors & IDEs

Operating Systems

Cloud & DevOps

Secrets & Env

Misc

.gitignore Output
75 lines
# ─────────────────────────────────────────────────────────────
# .gitignore — generated 2026-06-25
# Stacks: Node.js, Next.js, VS Code, macOS, Env / Secrets, Logs
# ─────────────────────────────────────────────────────────────
# Node.js
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
.npm
.yarn/cache
.yarn/unplugged
.yarn/build-state.yml
.pnp.*
*.tgz
.node_repl_history

# Next.js
.next/
out/
.vercel
next-env.d.ts

# VS Code
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
*.code-workspace
.history/

# macOS
.DS_Store
.AppleDouble
.LSOverride
Icon
._*
.DocumentRevisions-V100
.fseventsd
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns
.com.apple.timemachine.donotpresent
.AppleDB
.AppleDesktop
Network Trash Folder
Temporary Items
.apdisk

# Environment & Secrets
.env
.env.*
!.env.example
!.env.template
*.pem
*.key
*.p12
*.pfx
secrets.json
secrets.yaml
secrets.yml
credentials.json

# Logs
logs/
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*
.pnpm-debug.log*

How to use

  1. Click Copy .gitignore above.
  2. In your project root, create or open .gitignore.
  3. Paste and save — Git will immediately respect the new rules.
  4. Run git rm -r --cached . if you need to untrack already-committed files.
About

A gitignore generator lets you instantly build a clean, well-commented .gitignore file by selecting the languages, frameworks, editors, and operating systems your project uses. Instead of hunting through documentation or copying outdated snippets, simply tick Node.js, Python, macOS, Docker, VS Code — or any combination — and get a ready-to-paste file tailored to your exact stack in seconds.

FAQ
What is a .gitignore file and why do I need one?+

A .gitignore file tells Git which files and directories to exclude from version control. Without it, build artifacts, dependency folders like node_modules, secret .env files, and OS clutter like .DS_Store get accidentally committed and pushed, bloating your repository and potentially leaking credentials.

Can I combine multiple stacks in one .gitignore?+

Yes — that is exactly what this tool is for. Each stack you select contributes its own clearly labelled section, so the final file covers all your tools without duplication. A typical full-stack project might combine Node.js, Next.js, VS Code, macOS, and Env/Secrets.

What if I already committed files that should be ignored?+

Adding a .gitignore does not automatically untrack files already in your repository. After pasting the new file, run git rm -r --cached . to remove cached entries, then git add . and git commit. Git will stop tracking those files going forward while keeping them on disk.

How do I make exceptions inside a .gitignore rule?+

Prefix a pattern with ! to negate it. For example, .env ignores all .env files, while !.env.example keeps the example file tracked. The generated snippets already include common exception patterns like these for you.

Related tools