Select the languages, frameworks and tools in your project and build a .gitignore file combining the matching blocks. Copy or download the result. The patterns are embedded in the page — there is no call to any API.
Select at least one option above to generate the file.
The .gitignore file tells Git which files and folders should not
be tracked: installed dependencies (node_modules/, vendor/),
build artifacts (dist/, target/), environment files
(.env), caches, and operating system or editor metadata. Keeping them out of
the repository reduces its size, avoids conflicts, and prevents accidental leaking of secrets.
Each option corresponds to a block of patterns tested for that technology.
When you check several, the blocks are concatenated in order, each with a header comment
(for example # Node) so you know where each rule came from. You can copy the
content or download it already named .gitignore.
The tool covers a practical set: Node, Python, Java, Go, PHP, Ruby, Rust, .NET, the React and Angular frameworks, the VS Code and JetBrains editors, and the macOS, Windows and Linux operating systems. The patterns are a solid starting point — adjust them as your project needs.
No. To keep the site backend-free, the dataset is static and embedded in the page's own JavaScript. This means it works offline and without depending on external services, at the cost of not being as exhaustive as the official templates.
Yes — check as many as you want. Some patterns may repeat across blocks (for example
node_modules/ in both Node and React); this is harmless for Git.
In the repository root. Rules in a .gitignore apply to the folder where it is
located and its subfolders. Files already tracked by Git need to be removed from the index
(git rm --cached) for the ignore rule to take effect.