Closed ngan closed 10 years ago
We have a check called the migration
check. That check is enabled by defualt when you install the pre-commit
gem. The migration
check will look for instances where the migration directory was modified, but the schema was not updated as well:
If pre-commit
halts a check for any reason, you can always bypass running checks using git commit -n
. So, even if you have a migration error, you can still commit.
I'm going to close this issue, but if you feel that your question has not been answered properly, please feel free to reply and re-open the issue. ;)
Perfect!
Would be great to detect an addition/modification of files db/migration/* and a non-stashed schema.rb file that has been changed and ask the user to confirm if they wish to commit.