# ── Secrets / local config ─────────────────────────────────────────────
# Keep the base appsettings.json (no real secrets); ignore env-specific ones.
**/appsettings.*.json
!**/appsettings.json
.env
.env.*
!**/.env*.example

# ── .NET ───────────────────────────────────────────────────────────────
bin/
obj/
[Dd]ebug/
[Rr]elease/
*.user
.vs/
logs/
*.log

# ── Node / Next.js ─────────────────────────────────────────────────────
node_modules/
.next/
out/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*

# ── OS / editor ────────────────────────────────────────────────────────
.DS_Store
Thumbs.db
.idea/

# ── Migrations ─────────────────────────────────────────────────────────
# Reverted 2026-07-31: excluding new EF Core migrations while
# ErpDbContextModelSnapshot.cs stayed tracked meant every `dotnet ef
# migrations add` after the initial 4 silently produced a migration git would
# never see, while the (tracked) snapshot's changes committed normally —
# so the snapshot kept claiming tables existed that no migration in git
# history ever created them. Confirmed live: 25 HRM tables + 11 Manufacturing
# tables were missing from the actual database for exactly this reason.
# Migrations now stay tracked like any other source file — commit them.