Branching, environments & CI
You open a PR that adds a column to `likes`. A teammate reviewing it can read the diff, but not run it — the only Postgres anyone can test against is the shared dev database five other people are also using. Someone merges first, your migration collides with theirs, and now the whole team's local environment is broken until someone figures out whose change landed wrong. A branch per PR, built from nothing but your migrations, is how this stops happening.
try to break it
you drive.
The runner clones the repo at your commit. This step only sees files: your app code, and the supabase/migrations directory sitting inside it.
Toggle "migration has a bug" and replay. Notice Migrate and Seed are the only steps that can differ per PR — Clone, Pull, Health check and Configure are the same every time, because they never touch YOUR schema.