Work / Chitragupt / Wiki / Decisions
2026-05-30-foundational-env-files-committed
Decisioncanonicalverified 2026-06-26
DECISION.2026-05-30.FOUNDATIONAL-ENV-FILES-COMMITTED.env* files are committed
Note: Date
2026-05-30is a placeholder — the decision predates the log.
Decision
This is a private repo. .env, .env.local, .env.production, and any .env.* files are committed to git in every workspace.
Why
Private repo; user has explicitly chosen this trade-off so any agent or human cloning the repo has a working environment without separate secret-distribution.
Impact
- Do not gitignore
.env*. - Do not advise rotating secrets because they're "in git".
npx expo-doctor's "uncommitted env files" warning is intentional — ignore it.- Exception: flag before committing an unusually high-risk secret (private signing key, KMS root, prod DB root).
- Enforcement lives in root
CLAUDE.md.
Status
Active.
Sources
- .context/wiki/decisions/* § "(foundational, undated) —
.env*files are committed"
Every project of mine is written down like this.
Read the résumé