Gitignore Generator
Combine environment-specific patterns into a draft .gitignore. The output helps decide which untracked files belong outside a repository; it neither removes committed files nor retracts exposed secrets.
- Runs in your browser
- Nothing is uploaded
- No signup; device limits apply
Loading the tool. If it does not appear, reload this page.
How to use this tool
Select the languages and tools in use, then review each line against project policy. Some included presets ignore Cargo.lock or composer.lock, which may be essential to reproducible application installs.
Results and examples
A node_modules/ pattern excludes matching files that are not already tracked. Adding that pattern alone does not stop Git tracking a file that has previously been committed.
Limitations
- Lockfiles may belong in the repository; do not accept every preset without reviewing it.
- Ignoring a secret does not erase earlier commits or revoke the credential.
Fields
| Field | Guidance and constraints |
|---|---|
| Node.js | Check the unit and format displayed beside this field. |
| Python | Check the unit and format displayed beside this field. |
| Java / Maven / Gradle | Check the unit and format displayed beside this field. |
| Go | Check the unit and format displayed beside this field. |
| Rust | Check the unit and format displayed beside this field. |
| PHP / Composer | Check the unit and format displayed beside this field. |
| macOS | Check the unit and format displayed beside this field. |
| Windows | Check the unit and format displayed beside this field. |
| VS Code | Check the unit and format displayed beside this field. |
| JetBrains | Check the unit and format displayed beside this field. |
| .env / secrets | Check the unit and format displayed beside this field. |
| .gitignore | Check the unit and format displayed beside this field. |
Data handling
Processing stays in the current browser tab; the site does not upload tool input for the calculation itself.
Sources
Frequently asked questions
Does a pattern remove tracked files?
A node_modules/ pattern excludes matching files that are not already tracked. Adding that pattern alone does not stop Git tracking a file that has previously been committed.
Which preset choices need extra review?
Lockfiles may belong in the repository; do not accept every preset without reviewing it. Ignoring a secret does not erase earlier commits or revoke the credential.
