Pick your stacks and generate a .gitignore file with the right rules — Node, Python, Java, Go, React, Laravel and 15 more.
Every Git repository needs a .gitignore file, and every stack has its own set of files that should never be committed: node_modules in Node, __pycache__ in Python, the build directory in Java, vendor in PHP. Getting the list wrong means either committing binaries that bloat the repository or ignoring files that should be tracked. This tool lets you pick your stacks from a list of twenty and combines their templates into one file, with a comment header per section so you can see what came from where.
The templates follow the patterns published in the github/gitignore repository (CC0 1.0 license), the de facto standard that GitHub itself uses when you create a new repository. Each template covers the build outputs, dependency directories, IDE files, OS artifacts and environment files that the community has agreed should be ignored. When you select multiple stacks, the tool concatenates them in order — duplicates between stacks are harmless because Git processes .gitignore rules top to bottom and the first match wins.
The file is generated entirely in your browser. Nothing is uploaded, no API is called, and the result is plain text you can copy or download. If your project uses a combination not covered here — a monorepo with Go and React, for example — select both and the output covers both. The templates are reviewed periodically but stacks evolve: if you find a pattern missing, add it at the end of the file.
From the github/gitignore repository (CC0 1.0), the same source GitHub uses when you initialize a repository with a .gitignore. They are reviewed periodically.
Yes. Check as many as you need and the output concatenates them with a comment header per section.
No. The templates are embedded in the page and the file is assembled locally.
Add your own rules at the end of the generated file. The twenty stacks here cover the most common cases.
No. Git processes .gitignore rules top to bottom and a duplicate rule has no effect.
Vai.la turns any URL into a short link with click statistics, QR Code and your own biolink.
Vai.la is not responsible for how the tools are used or for decisions made based on their results.