Is it safe to use for production?

[9128305]

The pre-alpha status in pypi and lack of tests are concerning.

[browniebroke]

What do you mean by "lack of tests"? There is currently 86% test coverage which covers the main cases... Pre-alpha is probably something I could change, yes. I've used it on a couple of projects without issues. There is no need to have the app installed in production, as it's only used to re-create migration files, which you should you do in your local development environment anyway.

That being said, I don't know if lot of people other than me are using it successfully and it has a few rough edges, but should be simple to verify if it works in your setup.

After it ran, you can run a few commands:

1. python manage.py makemigrations should not detect any changes. I've seen it create an extra migration in some instances, but it was an earlier version
2. python manage.py showmigrations should list all migrations as remaked an unapplied
3. python manage.py migrate should not execute any migrations, and should fake apply all remaked migrations
4. running python manage.py showmigrations again should list all remaked migrations as applied

Test it locally (or somewhere where the DB can be recreated from scratch easily) first, and let me know if you hit any issues.

[9128305]

After deploying new remaked migrations should I remove replaces attributes in them?

[browniebroke]

Once it's fully deployed everywhere, yes. However, you don't have to do that to run remakemigrations again later

[9128305]

So if I want to revert to the old migrations, I can just delete the new one in django_migrations?

[browniebroke]

That's optional, the remaked migration contain the creation timestamp in their name so should be quite unique. AFAIK, Django doesn't care about rows from the django_migrations table which don't match a migration file on disk, they are pretty much ignored.

[9128305]

Much appreciated.