From 699f97d0934c219725ea21c1866d0ae7486dafeb Mon Sep 17 00:00:00 2001 From: clawbot Date: Sat, 28 Feb 2026 07:59:27 -0800 Subject: [PATCH] REPO_POLICIES: expand pre-1.0 schema migration rule (closes #5) --- prompts/REPO_POLICIES.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/prompts/REPO_POLICIES.md b/prompts/REPO_POLICIES.md index 5f8e062..a024cbd 100644 --- a/prompts/REPO_POLICIES.md +++ b/prompts/REPO_POLICIES.md @@ -144,8 +144,14 @@ style conventions are in separate documents: - Use SemVer. - Database migrations live in `internal/db/migrations/` and must be embedded in - the binary. Pre-1.0.0: modify existing migrations (no installed base assumed). - Post-1.0.0: add new migration files. + the binary. + - `000_migration.sql` — contains ONLY the creation of the migrations tracking + table itself. Nothing else. + - `001_schema.sql` — the full application schema. + - **Pre-1.0.0:** never add additional migration files (002, 003, etc.). There + is no installed base to migrate. Edit `001_schema.sql` directly. + - **Post-1.0.0:** add new numbered migration files for each schema change. + Never edit existing migrations after release. - All repos should have an `.editorconfig` enforcing the project's indentation settings.