Lucas BergerandClaude Opus 5
28e0fdb631
A pattern with no leading slash already matched at any depth, but the intent was not obvious from the rules. State it explicitly and widen to `.env.*` so variants like .env.local or .env.unraid-api cannot slip through, while keeping .env.example and .env.<name>.example tracked. Verified with git check-ignore at the repo root, one level down, and three levels down. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
16 lines
711 B
Plaintext
16 lines
711 B
Plaintext
# Secrets — every collection keeps its own .env beside its .env.example.
|
|
# A pattern with no leading slash matches at EVERY depth, so these cover any
|
|
# .env anywhere in the repo, present or future. `.env.*` catches variants like
|
|
# .env.local / .env.unraid-api; the negation keeps the committed examples.
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
!.env.*.example
|
|
|
|
# MemPalace per-project files (issue #185).
|
|
# `mempalace init` ignores both by default. We deliberately track mempalace.yaml —
|
|
# it is just wing/room config, and losing it on a fresh clone would make mining
|
|
# fall back to basename auto-detection (wing "scripts", which collides).
|
|
# entities.json stays ignored: it holds detected people/entities.
|
|
entities.json
|