77ac9a01b5
Both lockfiles were updated on every npm install, creating a drift surface for nothing. CI, Docker and dev all use npm, so yarn.lock has no consumer. Add it to .gitignore so future yarn-curious developers don't accidentally re-introduce it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
20 lines
285 B
Plaintext
20 lines
285 B
Plaintext
# Runtime data (Docker volumes)
|
|
data/
|
|
import-data/
|
|
import/
|
|
gitea/
|
|
|
|
# Secrets
|
|
.env
|
|
|
|
# Dev scripts / DB dumps
|
|
scripts/large-data.sql
|
|
|
|
.vitest-attachments
|
|
**/test-results/
|
|
.worktrees/
|
|
.superpowers/
|
|
|
|
# Repo uses npm; yarn.lock is ignored to avoid double-lockfile drift.
|
|
frontend/yarn.lock
|