Choose your templates
Search language, framework and tool templates. Add only the rules your project needs.
YOUR REPOSITORY, LESS CLUTTER
Build your .gitignore
Choose your languages, tools and systems. Combine templates, review the rules, and save one file.
Templates & preview
Select templates
.gitignoreSelected templates
No templates yet
You can combine language, framework, operating system and editor templates. Review the rules for your project.
.gitignore
# Select a template to see your file here.Templates load from this site; generation happens in your browser.
Related usage notes
Python usage notes
- Ignore local virtual environments such as .venv and generated Python bytecode.
- Decide deliberately whether a project-specific configuration file belongs in Git.
- Add your editor or operating system template only when those rules belong in this repository.
Watch out: Do not assume every lock file or requirements file is disposable. Dependency declarations are often essential project source.
Check what Git will ignore
git check-ignore -v .venv/bin/pythonThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesNode.js usage notes
- Keep node_modules out of Git; reinstall it from your package manifest.
- Review framework directories such as dist, build or .next for the actual project.
- Keep the package lock file when your team relies on reproducible installs.
Watch out: Do not assume .env.example contains secrets; it is often useful configuration documentation to commit. Check its contents before sharing.
Check what Git will ignore
git check-ignore -v node_modules/example/index.jsThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesJava + Gradle usage notes
- Ignore compiled classes and build output.
- Keep gradlew, gradlew.bat and Gradle wrapper configuration under version control.
- Add IDE rules only if your team agrees those files are local rather than shared.
Watch out: Review generated archives individually; a checked-in release artifact may be intentional.
Check what Git will ignore
git check-ignore -v app/build/classes/java/main/App.classThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesGo usage notes
- Ignore local executables and temporary coverage output where appropriate.
- Keep go.mod and go.sum as project inputs.
- Treat vendor directories according to your repository policy rather than a blanket rule.
Watch out: A broad binary filename pattern may hide a file you intended to commit; inspect the preview first.
Check what Git will ignore
git check-ignore -v coverage.outThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesAndroid usage notes
- Exclude local.properties because it commonly holds a machine-specific SDK path.
- Keep the Gradle wrapper and project build files.
- Handle signing files and credentials deliberately; never publish private keys.
Watch out: Some IDE configuration can be shared by a team. Review the rules before accepting every IDE exclusion.
Check what Git will ignore
git check-ignore -v local.propertiesThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesuni-app / HBuilderX usage notes
- Keep pages.json, manifest.json, source directories and project uni_modules when they are part of your app.
- Exclude generated unpackage output unless your workflow intentionally versions specific files there.
- Check whether local HBuilderX settings should be shared by your team.
- Installed node_modules can be restored from dependency manifests and normally do not belong in Git.
Watch out: Before using a broad unpackage rule, check whether your project stores required resources under that directory. If files are already tracked by Git, adding .gitignore rules will not stop tracking them.
Check what Git will ignore
git check-ignore -v unpackage/dist/dev/app-plus/index.htmlThe output identifies the matching rule and source file. If nothing appears, check the path and whether the file is already tracked.
Troubleshoot ignore rulesReview the rules
Check the preview and add your own rules. Order and negation patterns matter.
Save and verify
Download .gitignore to your repository. Use git check-ignore -v to inspect a rule; tracked files need a separate step.