1001Ferramentas
Tools Categories Guides FAQ
About Contact Privacy Policy Terms of Use
🚫Dev

.gitignore Generator

Generate a .gitignore by combining language/IDE templates — Node, Python, Java, Go, Rust, .DS_Store, JetBrains, VSCode etc. Everything in your browser.

Templates

Build your .gitignore to fit

Opening a project without a decent .gitignore is asking to version things that should never reach the repository: dependencies, build artifacts, IDE settings. This generator combines ready-made templates for your stack and hands back a complete .gitignore.

Tick the languages, tools and environments you use (Node, Python, Java, Go, Rust, plus macOS's .DS_Store and editor folders like JetBrains and VSCode). The tool merges it all into a single file with no repeated rules. That way only what truly matters reaches git.

Generation happens in the browser itself, and the result comes out ready to copy into the project root. A small step that spares you plenty of headaches down the line.

Frequently asked questions

Does it strip repeated rules when I tick several templates?
It doesn't. Every ticked template becomes a block with a comment header and all of its lines, even where a rule already showed up earlier. Tick Node and Python together and dist/ appears twice; Python with Java repeats build/; Node with Logs repeats *.log; Node with Env repeats .env; Java with JetBrains repeats *.iml. A duplicate in .gitignore breaks nothing, git simply ignores the path again, but delete them by hand after copying if it bothers you.
Is the result the same as GitHub's official template for the language?
It's a good deal shorter. Each block here runs four to ten lines with the essentials: the Node one covers node_modules/, npm and yarn logs, .env, dist/ and coverage/, whereas the Node.gitignore file GitHub maintains runs past a hundred lines and anticipates tooling most projects never touch. To open a repository the lean version usually suffices; for anything specific, like Nuxt, Serverless or Parcel, add the line yourself.
Why does the block order change when I untick and tick again?
The output follows the order in which you selected, not the order of the buttons on screen. The page opens with Node, macOS and VSCode on; untick Node, tick it again, and it moves to the end of the list, taking its block down with it. This changes nothing about how the file behaves: git evaluates every pattern, and order would only matter with negation rules, those lines starting with !, which none of these templates use.

Related Tools

🔍

.git-blame-ignore-revs Generator

List of commit hashes for Git to ignore in blame (mass formatters: prettier, black, eslint --fix). Useful for large refactors.
🐳

Dockerfile Generator

Build a Dockerfile from common templates: Node, Python, Go, Static Nginx, with optional multi-stage, healthcheck and non-root user. Everything in your browser.
📧

.mailmap (Git) Generator

Map inconsistent names and emails to a single author in Git, improving stats and shortlog. Official format.
🌳

Git Aliases Generator

Useful git aliases (st, co, br, lg, undo, save, wip, amend, hist) ready to paste into .gitconfig.
🌿

Git Cheatsheet

Searchable list of the most-used git commands — config, commit, branch, merge, rebase, stash, log, remote, reset. With copyable examples. Everything in your browser.
📜

.gitattributes Generator

Generate .gitattributes to normalize line endings, mark binaries, configure diff and override GitHub linguist language stats.