Write a .gitignore without remembering every rule

node_modules, __pycache__, .DS_Store, target/ — combine the standard sections for your stack into one file instead of copying fragments from old projects.

Tools used in this guide

The job

A missing .gitignore means build output, dependency folders, and OS junk get committed — and removing them later is tedious. The standard patterns exist; assembling them per-stack is the annoying part.

How to do it

Check the stacks you use — Node.js, Python, Java/Gradle, Go, Rust, Unity, plus OS and editor noise — then generate. Sections come out labelled, with duplicate lines removed while order is kept.

Ten templates cover common language toolchains, .DS_Store / Thumbs.db, and IDE folders like .idea/ and .vscode/.
Copy the text or download it named .gitignore directly.

Worked example

A Next.js project on a Mac with VS Code: check Node.js, macOS, and VS Code — the output covers node_modules/, .next/, .DS_Store, and editor workspace files in one file.

Limits

The templates cover the common cases, not every framework. Review the generated file before committing — your project may need additional entries like environment files (which you should handle deliberately) or custom build directories.