Before applying the five pending migrations I took a full snapshot of the live database — every table plus the source of all 61 functions. It sits in .backups/ and holds 852 personnel records, so it must never be committed. The ignore rule comes first, on its own, rather than riding along with the next change: a snapshot that is already staged when someone remembers to add the rule is a snapshot that has been in a commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
60 lines
1.0 KiB
Plaintext
60 lines
1.0 KiB
Plaintext
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
|
||
|
||
# dependencies
|
||
/node_modules
|
||
/.pnp
|
||
.pnp.*
|
||
.yarn/*
|
||
!.yarn/patches
|
||
!.yarn/plugins
|
||
!.yarn/releases
|
||
!.yarn/versions
|
||
|
||
# testing
|
||
/coverage
|
||
|
||
# next.js
|
||
/.next/
|
||
/out/
|
||
|
||
# production
|
||
/build
|
||
|
||
# misc
|
||
.DS_Store
|
||
*.pem
|
||
|
||
# debug
|
||
npm-debug.log*
|
||
yarn-debug.log*
|
||
yarn-error.log*
|
||
.pnpm-debug.log*
|
||
|
||
# env files (can opt-in for committing if needed)
|
||
.env*
|
||
!.env.example
|
||
|
||
# vercel
|
||
.vercel
|
||
|
||
# typescript
|
||
*.tsbuildinfo
|
||
next-env.d.ts
|
||
|
||
# supabase CLI local dev (generated, project-machine-specific)
|
||
/supabase/.branches
|
||
/supabase/.temp
|
||
/supabase/snippets
|
||
|
||
# scratch output of `npm run types:generate`, for comparing against the
|
||
# hand-written lib/supabase/types.ts — never itself imported
|
||
/lib/supabase/types.generated.ts
|
||
|
||
# local scratch scripts/screenshots (ad-hoc verification against a real or
|
||
# seeded DB — can carry HR data or use SUPABASE_SERVICE_ROLE_KEY; never commit)
|
||
.scratch_*
|
||
/.scratch_shots/
|
||
|
||
# Datenbank-Sicherungen (enthalten Personendaten) – nie committen.
|
||
.backups/
|