Same reasoning as scheduled-emails.json: it's mutated by the running app (site banner content), not source. readBanner() already falls back to sane defaults when the file is missing, so untracking it is safe for fresh checkouts. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
40 lines
505 B
Plaintext
40 lines
505 B
Plaintext
# dependencies
|
|
node_modules/
|
|
|
|
# env files (never commit real secrets — .env.example files are fine)
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
|
|
# IDE
|
|
.idea/
|
|
.vscode/
|
|
|
|
# next.js
|
|
.next/
|
|
out/
|
|
|
|
# build output
|
|
dist/
|
|
build/
|
|
|
|
# logs
|
|
npm-debug.log*
|
|
yarn-debug.log*
|
|
yarn-error.log*
|
|
*.log
|
|
|
|
# typescript
|
|
*.tsbuildinfo
|
|
|
|
# OS
|
|
.DS_Store
|
|
Thumbs.db
|
|
|
|
# misc scratch / generated files
|
|
temp/
|
|
backend/public/uploads/
|
|
|
|
# runtime data stores (mutated by the running app, not source)
|
|
backend/data/scheduled-emails.json
|
|
backend/data/banner.json |