Run database migrations as a controlled, gated step

Run database migrations as a controlled, gated step | BeforeMerge Rules | BeforeMerge

Why this matters

Database changes are the highest-risk part of a deploy and the hardest to undo. Migrations should be versioned, reviewed, run as an explicit gated step, and designed backward-compatible so app and schema can roll forward safely.

Bad

psql prod -c "ALTER TABLE users DROP COLUMN email;"  # ad hoc, irreversible

Good

# reviewed migration file, run as a dedicated gated CI step
npm run migrate:up   # versioned, ordered, backward-compatible

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters