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 On Saturday, April 9, 2016 at 9:52:27 AM UTC-4, jorr...@gmail.com wrote: > > 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). > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/eed606ed-0f95-4c23-8210-035ebc028998%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
