How to know which models have changed and need make migrations?

[Neto]

In my localhost is everything migrated, but in production have "Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them."

How to know which models have changed and need make migrations? Exist a command to know?

[Daniel Roseman]

You shouldn't ever need to make migrations in production. You make them in dev, commit to source control, deploy along with the rest of the code, then run the migrations in prod.

--
DR.

[Neto]

I know, but in production is showing the message that I have to do makemigrations.

I need a command to know what models need to makemigrations

[C. Kirby]

Are you sure you are adding your new migrations to your source control? It sounds like the model changes  are being correctly commited but the generated migrations are not.

[jorr...@gmail.com]

I've run into the problem of migration files not being added to source control with PyCharm because PyCharm doesn't seem to automatically commit auto-created files unless you explicitly tell it to in the settings (and even then it doesn't always work).

[Tim Graham]

Also, your models might reference a setting whose value differs between development and production. This probably won't cause any problems but will trip up the migrations autodetector into thinking that a migration needs to be made.

https://code.djangoproject.com/ticket/24648