This migration is produced automatically by makemigrations on project using hordak 1.6.0. This commit seems to address this issue.
Basically, I include makemigrations (grepping for expected No changes detected output) call into my CI pipeline to catch all non-migrated model changes, and it seems that the same step could be included in this project CI.
Coverage remained the same at 95.408% when pulling f095f32e8607932500b08ced6161993cc73a3436 on pavel64-sutyrin:master into e3d1e0555f9ad94294da4cac7d004cc183f908b2 on adamcharnock:master.
This migration is produced automatically by
makemigrations
on project using hordak1.6.0
. This commit seems to address this issue.Basically, I include
makemigrations
(grepping for expectedNo changes detected
output) call into my CI pipeline to catch all non-migrated model changes, and it seems that the same step could be included in this project CI.