EdTech Tracker

← Coding lens

gitignore

tool judged 8% likely a named technique or architecture

First seen
2026-03-20
Independent sources
4
Articles
6
Last 4 weeks vs prior
0 vs 4

See how it has spread across media tiers

Mentions over time

Articles per week (by publish date) using the term, in any spelling.
01.532026-W112026-W402026-W41
Table view
WeekArticlesSources
2026-W1111
2026-W3711
2026-W4032
2026-W4111

In their words

A tutorial mentioned a .gitignore , and you're not sure what goes in it.

config.example.js becomes config.js with real values, and .gitignore never hears about it.

Asked to clean up untracked files, it answered: rm -f .env.example .gitignore README.md tmp-notes.txt && rm -rf experiments/ build/ packages/a/node_modules/ packages/b/node_modules/ That deletes three tracked files.

The comment in the code says it plainly: "This is worktree hygiene, not policy — we never touch the product repo's .gitignore." The loop got smarter because it failed in public.

ignore became the crate of the same name with the same gitignore semantics.

(2) Never commit .env files to git — add .env to .gitignore.