Migrations missing related to ordering

[peterbe]

Now I'm getting this:

▶ ./manage.py migrate
/Users/peterbe/virtualenvs/normandy/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
  """)
Operations to perform:
  Apply all migrations: admin, auth, base, contenttypes, recipes, sessions, studies
Running migrations:
  No migrations to apply.
  Your models have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
(normandy)

I git pulled master. Not sure where it comes from.

[peterbe]

For what it's worth, this is the migration it wants to create:

# normandy/recipes/migrations/0013_auto_20181018_1732.py

class Migration(migrations.Migration):

    dependencies = [
        ('recipes', '0012_reciperevision_bug_number'),
    ]

    operations = [
        migrations.AlterModelOptions(
            name='action',
            options={'ordering': ('id',)},
        ),
        migrations.AlterModelOptions(
            name='approvalrequest',
            options={'ordering': ('id',)},
        ),
    ]

[peterbe]

Any idea @mythmon ?

[mythmon]

This probably came up in #1550, since I changed the ordering fields. I always forget that affects the migrations. We should probably make the migration it wants.

It would be lovely to have a CI job that checked for this and failed if there were any migrations that would be created.

[peterbe]

It would be lovely to have a CI job that checked for this and failed if there were any migrations that would be created.

That's a great idea. I think this can actually be done with ./manage.py makemigrations --check.

I'll file an issue and try it out.