From b9efe81becbf91f61a46452c7d4f295100c2c691 Mon Sep 17 00:00:00 2001 From: Maximilian Stubhan Date: Mon, 3 Aug 2026 09:57:25 +0200 Subject: [PATCH] Keep database snapshots out of the repository MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitignore b/.gitignore index 60d86fe..29805da 100644 --- a/.gitignore +++ b/.gitignore @@ -54,3 +54,6 @@ next-env.d.ts # seeded DB — can carry HR data or use SUPABASE_SERVICE_ROLE_KEY; never commit) .scratch_* /.scratch_shots/ + +# Datenbank-Sicherungen (enthalten Personendaten) – nie committen. +.backups/