In Django\'s migrations code, there\'s a squashmigrations
command which: \"Squashes the migrations for app_label
up to and including migratio
You can just delete the migration files and run makemigrations
again. If you have a dev deployment that uses these, you should migrate back to the one before the first one you delete.
Also, it's probably a good idea to commit your code first, in case something goes wrong.
Also:
The slight complication with this is that if there's custom RunPython code, it won't be included in the new migration created by makemigrations