repost schema migrate status checks the migration history and writes nothing. It exits 0 when the history is clean and 1 on any finding, with one line per finding on stdout, which makes it the standard pull-request gate alongside validate and generate --check.
Usage#
repost schema migrate status [options]Options#
| Option | Description |
|---|---|
--schema <path> | A .repost file or a directory of them. Defaults to ./repost/schema.repost, else ./repost/schema/. |
Findings#
| Finding | Line printed |
|---|---|
| Clean, linear history | Up to date. The schema matches the latest migration and the lineage is linear. |
| No migrations yet | No migrations yet. Run `repost schema migrate dev --name init` to create the first. |
| Unmigrated changes | unmigrated changes: <n> event type(s) differ from the last snapshot; run `repost schema migrate dev` |
| Fork | fork detected: followed by both head directories. |
| Tampered snapshot | checksum mismatch: migration <id> records <hash> but its schemas.json now hashes to <hash> (edited or corrupted) |
Example#
- run: repost schema validate
- run: repost schema migrate status
- run: repost schema generate --check