About

Tool No. 60 of Pikkola

A .gitignore records decisions about what belongs to a repository and what belongs to one machine. Most of it is written once and never read again, which is how a wrong line survives for years. This page writes one, and then tests paths against it instead of trusting it.

What it does

How the file is assembled

The guard comes first, then languages, then platforms, operating systems and editors, each in the order of the catalogue. The order you press the chips in does not matter, so the same selection always produces the same bytes and two people can read the same file. A line a later section also wants is skipped there; if a section loses every line that way, its heading goes too.

Blank lines separate sections and the file ends with a newline. Nothing else is added: no date, no generated-by comment, no editor setting. What you download is exactly what you reviewed above it.

How a path is decided

Each line becomes a pattern, the patterns are tried against the path in order, and the last one that matches decides. If none matches, the file stays tracked. Before the path itself, every folder above it is tested: if one is excluded, the path is excluded as well, and the panel names that folder, because git never enters an excluded folder.

All of this is applied to one file, read as if it sat at the root of the repository.

Where the limits are

Why it is free

Pikkola builds small tools with one job each and keeps them free, with no account and no lock on the result. A page that runs in the browser costs almost nothing to serve, so there is no reason to charge for it or to watch who uses it.

Contact

A stack that belongs in the list, a path this page decides differently from git, a Korean or Japanese sentence that reads badly: hello@pikkola.com. The rule lines and the path are the most useful thing to send.

Back to the studio