Attach a review instruction to database migrations
Put the migration convention in a scoped rule so it follows the repository through code review.
Limit the instruction to migration files#
Use a stable key and the repository-relative directory containing migrations. Give reviewers a concrete condition to check.
version: 2
rules:
- key: invoice-backfill
path_globs: ["db/migrations/**"]
text: Check that the backfill can resume after a partially processed batch.
In a change touching a migration and a README, the path condition identifies the migration. When you revise the wording, preserve the key so the instruction retains its identity.