postgres/edited-migrations
Checks that no migration at or before postgres.frozen_through differs from its committed text.
Part of the postgres configuration, at the recommended level. It runs at the commit stage, once per scope. gspot runs this check itself.
An applied migration never runs again, so an edit reaches only new databases, and environments drift apart.
What to do
Section titled “What to do”Restore the file with git checkout, and write the change as a new migration.
Example
Section titled “Example”An edit to a committed migration reports a finding. Restore the original file, and write the change as a new migration.
Turn it off
Section titled “Turn it off”Turn it off for some files, with a reason:
gspot ignore postgres/edited-migrations --paths "<glob>" --reason "<why>"