From 8e2b7f4c3ece96cf33f4ab54a1bcd2542d0a40bf Mon Sep 17 00:00:00 2001 From: "Enot (ded) Skelly" Date: Tue, 9 Jun 2026 08:32:36 -0700 Subject: [PATCH] docs: update schema migration notes --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6ff71cb..88b48e8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -78,8 +78,9 @@ swag init # if you changed any handler or api type (see below) All schema changes must include a proper migration path: -- Add SQL to `db/migrations/001_schema.sql` (we use a single migration file for - now — append to the appropriate section with a comment) +- Add a new migration file to `db/migrations/` following the existing naming + convention (e.g. `002_add_observation_count.sql`). Do not modify existing + migration files — append only via new files. - Update `db/queries/queries.sql` with any new or modified queries - Re-run `sqlc generate` to regenerate `db/sqlc/` - Update the store layer in `db/` to expose the new functionality