Generator voor .gitignore-bestanden
Bouw een .gitignore van veelvoorkomende sjablonen: Node, Python, Java, Go, Rust, macOS, Windows en IDE's.
Snel antwoord: Generator voor .gitignore-bestanden: maak een .gitignore op basis van veelgebruikte sjablonen voor Node, Python, Java, Go, Rust, macOS, Windows en IDE's. Werkt volledig in je browser, gratis en zonder registratie.
Laatst bijgewerkt
Goed om te weten
A .gitignore file keeps clutter and secrets out of version control by telling Git which paths to leave untracked — build artifacts, dependency folders, editor droppings and OS metadata. Getting this right early matters, because once a file has been committed, adding it to .gitignore afterward does not remove it from the repository; you have to run git rm --cached to stop tracking it. Starting from a solid template avoids that cleanup headache entirely.
The patterns follow well-known conventions: a trailing slash like node_modules/ matches directories, a leading slash anchors a pattern to the repo root, and a line beginning with ! re-includes something a broader rule excluded. This generator stitches together the canonical ignore sets for each ecosystem you toggle — Node's node_modules and logs, Python's __pycache__ and virtual environments, and so on — plus the OS and editor files (.DS_Store, Thumbs.db, IDE folders) that clutter almost every project regardless of language.
A frequently overlooked point is that .gitignore is about untracked files only, and it is emphatically not a security mechanism — never rely on it to keep an already-committed secret out of history. For sensitive values, keep a real secrets manager and rotate anything that leaked. You can nest a .gitignore in a subdirectory for finer control, and paste your own extra patterns at the bottom. Round out a new repository with the license generator and a starter README.
Veelgestelde vragen
- Is de .gitignore-generator gratis?
- Ja — gratis zonder registratie.
- Welke sjablonen zijn inbegrepen?
- Node, Python, Java, Go, Rust, macOS, Windows en veelgebruikte IDE's (VS Code, IntelliJ, vim).
- Worden mijn keuzes geüpload?
- Nee — elke regel is ingebouwd in de pagina.
- Kan ik aangepaste patronen toevoegen?
- Ja — kopieer de output en voeg je eigen patronen onderaan toe.
- Waar moet de .gitignore zich bevinden?
- In de root van je repo. Je kunt ook geneste .gitignore-bestanden in submappen hebben voor meer controle.