The official github/gitignore templates for Node, Python, Java, Unity and more, merged
Runs in your browser. Nothing you type is sent anywhere. Checked against sources on 16 Oct 2026.GitHub keeps one .gitignore template per language, framework and editor, the same ones offered when you create a repository. This page has 61 of them, from Node.js and Python to Unity, Terraform and JetBrains. Tap several and they are merged into one file, with each block headed by its name and any rule repeated in a later block removed when removing it changes nothing.
Set the options you need, or start from the example.
The result is made again every time you change something.
Copy it or download it. Nothing was sent anywhere.
Every new repository needs a .gitignore before the first commit, or build output, dependencies and editor settings end up in history. GitHub publishes one template per language, framework, editor and operating system; this page has 61 of them, at a fixed commit, and merges the ones you tap into a single file.
Merging without surprises. Templates overlap: Node.js, Next.js and NestJS all ignore logs. A repeated line is removed only when no ! rule stands between the two copies, so the merged file ignores exactly what the templates ignore one after another. The page says how many lines it removed.
The path tester was checked against git check-ignore on more than 1,000 paths, across hand-written rule sets and real templates. Everything runs in your browser; nothing you type is sent anywhere.
The rest of the article, and all 6 questions about .gitignore Generator, are on the .gitignore Generator page.
Save it as .gitignore, with the leading dot and no extension, in the top folder of the repository, next to the .git folder. Patterns with a slash at the start or in the middle are read from that folder. A .gitignore in a subfolder also works and applies only below it.
A .gitignore only affects files git is not tracking yet. Once a file has been committed, git keeps following it. Run git rm --cached followed by the path, commit, and from then on the rule applies. The file stays on your disk; only its copy in the index goes.
Yes. The 61 texts come unchanged from the github/gitignore repository at a fixed commit, the collection GitHub uses when you create a repository, published under the CC0 licence. Each block in the result is headed with the template name, so you can see where a rule came from.
Yes, as git is on Linux and in most CI systems, so Build/ does not match a folder named build. On Windows and macOS, git usually sets core.ignorecase to true and ignores case, so a pattern may match locally but not on the build server. Write patterns in the exact case of the files.
Rates and rules change; check the source before you rely on a figure.
Still stuck? Ask about .gitignore Generator and anybody who knows can answer. No account needed.
Same job, other tools: Block AI Crawlers – Keep model crawlers out while search crawlers carry on.
On the related tools: Cron Expression Generator – Generate a cron expression by choosing when the job should run · Sitemap Index Generator – Split a large site into numbered sitemaps with an index file.