DevOps Generators

Gitignore Generator

All tools

Pick one or more stacks and copy a compact .gitignore to build on.

How it works

Four simple steps

1

Toggle your stacks

Click Node, Python, React, Laravel or Go to add their patterns.

2

Combine blocks

Selected stacks merge into one file, each under a comment heading.

3

Add project paths

Type extra patterns into the output once your stacks are chosen.

4

Copy to .gitignore

Paste the text into a .gitignore file at the repository root.

Gitignore Generator

About Gitignore Generator

You just ran git init on a new project, and the first git status lists node_modules, a virtual environment and a .env file. Before the first commit you need an ignore file that keeps those out.

Click a stack button to toggle it. Node, Python, React, Laravel and Go are available, and you can select several for a repo that mixes them. Each block is added under its own # heading. The lists are deliberately short, covering dependency folders, build output, caches and .env files rather than the exhaustive templates some projects use. The output box is editable, so add your own paths (IDE folders, logs, local data) after you finish picking stacks, because toggling a button rebuilds the text.

Two things to review. Combining Node and React repeats lines such as node_modules/, which is harmless but untidy. The Go block ignores vendor/, so delete that line if your team commits vendored modules. And remember that .gitignore does not untrack files already committed; run git rm --cached on those first.

The list is assembled on the page and copied with one button, with no download step. If credentials were committed before the ignore file existed, paste the suspect files into the Secrets Scanner. The Large File Detector spots binaries worth ignoring, and the README generator drafts the other first-commit file.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

Ignore rules only apply to untracked files. If the file was committed earlier, remove it from the index with git rm --cached and commit that change, and the rule takes effect.

Clicking a stack button rebuilds the output from the selected templates and replaces the text. Pick all your stacks first, then add custom lines.

For files holding real credentials, yes. Many teams commit a .env.example with placeholder values so new developers know which variables to set. These templates do not ignore that file.

View more FAQs

Related tools

View all

Kubernetes Manifest Studio

Generate Deployment, Service, and Ingress YAML with a drift checklist.

Open

K8s Inspector

Summarize Kubernetes YAML kinds, names, and labels.

Open

K8s Resource Diff

Diff two Kubernetes manifests locally.

Open

K8s Manifest Splitter

Split multi-document YAML into one file per resource.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools