Pick the stacks you are using and get a single clean .gitignore, with the overlapping rules removed. That deduplication is the reason to use a tool rather than pasting templates end to end: nearly every stack ignores build output, logs and editor files, so Node plus React plus VS Code gives you node_modules/ three times and a file nobody wants to read. Here each rule appears once, under the section that introduced it, with headers so you can still see where everything came from. Selection order does not affect the output, so regenerating the file later produces exactly the same bytes and does not show up as a diff. You can search templates by the rule you are trying to ignore, add your own rules at the end, and download the file directly. Everything runs in your browser.
| Pattern | Matches |
|---|---|
| node_modules/ | That directory anywhere in the tree (trailing slash = directory only) |
| *.log | Any file ending .log, at any depth |
| /build | Only build at the repository root, not nested ones |
| !important.log | An exception — re-includes a file an earlier rule excluded |
| **/temp | temp at any depth, explicitly |
| debug?.log | debug1.log, debugA.log — one character wildcard |
Because templates overlap heavily. Pasting Node, React and VS Code together repeats node_modules/, dist/ and log rules several times over. Git handles the duplication fine, but the file becomes hard to read and hard to review. Here each rule appears once, under the first section that needed it.
They are a curated subset of github/gitignore, the collection GitHub offers when you create a repository. It is public domain. They are bundled with the page rather than fetched, so the tool works offline and cannot break when a file is renamed upstream.
Almost always yes, and there is a dedicated Secrets template for it. One caveat worth knowing: adding a rule does not remove a file Git is already tracking. If a secret has been committed, ignoring it now changes nothing — you need to remove it from the index and, if it reached a shared branch, rotate it.
Because templates are emitted in catalogue order rather than the order you clicked them. Without that, two people picking the same stacks would produce files that differ only in ordering, and every regeneration would show up as a diff.
Yes — anything you type is appended in a Custom section at the end, with anything already covered above skipped. Putting them last means they are easy to spot when reviewing the file later.
No. The templates are local and the file is assembled in your browser. Custom rules, which sometimes name internal paths or filenames, are never sent to a server.
Templates are a curated subset of the github/gitignore repository, which is public domain, bundled locally so the tool works offline and cannot break when a file is renamed upstream. The merge is the part that matters. Stacks overlap heavily — nearly every one ignores build output, logs and editor droppings — so concatenating Node, React and VS Code emits node_modules/ three times. Every rule is checked against what has already been written and skipped if it is a repeat, with the first occurrence kept so a rule stays under the section that introduced it rather than being hoisted somewhere confusing. A template whose rules turn out to be entirely covered by earlier ones is dropped rather than leaving a section header with nothing beneath it. Templates are emitted in catalogue order rather than the order they were clicked, so the same selection always produces byte-identical output — which keeps the file out of diffs when a colleague regenerates it. Custom rules are appended last and deduplicated against everything above them, and the file ends with exactly one trailing newline, since omitting it makes Git annotate every future diff of the last line.