Gitignore Generator

Frequently Asked Questions

Common questions about the free online gitignore generator.

Tick the sections that match your project, click Build .gitignore, then download the file or copy the text into a file named .gitignore.

Put it in the root of your repository. Git applies those rules to the whole project, and you can add more .gitignore files in subfolders.

Node, Python, Java, Go and Rust, plus editor and IDE files, macOS, Windows and Linux clutter, logs and caches, and secret or environment files.

A new rule does not untrack a file. Run git rm --cached path on the file, commit, and Git will start ignoring it from then on.

Yes. Committing it shares the ignore rules with your team so nobody accidentally adds build output or secrets to the repository.

Use .git/info/exclude for rules you do not want to share, and keep the committed .gitignore for rules the whole team needs.

A leading exclamation mark re-includes a file that a previous rule ignored, such as keeping .env.example while ignoring other .env files.

No. The file is assembled from the templates in your browser and is never sent anywhere.

Yes. It is plain text, so add, reorder or delete any line after downloading or pasting it into your project.

Yes. The generator is fully responsive and the output can be copied into a mobile Git client or editor.