block .gitignore Generator star

How It Works

Check the boxes for whatever applies to your project — a language or runtime like Node.js, Python or Java, an operating system like macOS, Windows or Linux, an editor like VS Code or IntelliJ/JetBrains, plus Git's own leftover files and a block for .env and secrets. Each checkbox adds a small, well-established set of ignore patterns pulled from the conventions the community actually uses — node_modules/ for Node, __pycache__/ and .venv/ for Python, *.class and target/ for Java, .DS_Store for macOS, Thumbs.db for Windows, and so on. As you check more boxes the tool merges everything into one list, drops exact duplicates, and shows the result live in a text box you can copy or download directly as a file named .gitignore.

The reason to combine categories rather than write one from scratch is that most real projects straddle several of them at once: a Node.js API developed on a Mac in VS Code needs the Node block for build artifacts, the macOS block so .DS_Store never sneaks into a pull request, and the VS Code block so your personal editor settings do not overwrite a teammate's. Checking all three and downloading once is faster and less error-prone than hand-assembling patterns from memory or copy-pasting fragments from old projects.

Good to Know

A .gitignore file only affects files Git does not know about yet — it tells Git which untracked files to leave out of git status, git add . and future commits. It has no effect on files that are already tracked (already committed at least once). This is the single most common point of confusion: adding .env to .gitignore after it was already committed does not remove it from the repository or stop Git from tracking further changes to it. To actually untrack a file, you first need to run git rm --cached <file> (which removes it from Git's index but leaves it on disk), commit that removal, and only then does the matching .gitignore rule take over for the future.

Most of the patterns offered here trace back to GitHub's official github/gitignore repository, the most widely referenced source for language- and tool-specific templates and the same collection GitHub itself offers when you create a new repository through its web UI. Keeping dependency folders like node_modules/ and build output like dist/ or target/ out of version control matters for size — these folders can easily outweigh your actual source code many times over and are trivially regenerated from a lockfile or build script — while keeping files like .env, *.pem and *.key out matters for security: committing a secret to Git history means it is effectively public forever, since removing it from the latest commit does not erase it from earlier ones without rewriting history entirely.