django-unmigrate 0.1.3

If you are in a complex Django project, sometimes you will find yourself switching between multiple branches, some of which can add a number of database migrations. Before switching back to master you will have to unapply all migrations that are specific to the current branch. In order to unapply these migrations, you have to enter the migration that comes right before the first migration of the current branch. If more than one of your apps are involved, you will have to do that for each one of them.

If you leave your migration names unchanged, inferring the name of the right migration to target is not too difficult - Django is smart enough to let you use an unambiguous prefix of any migration name. But if you have renamed your migrations as this article recommends, then you need to do the searching manually.

With django-unmigrate you can speed up the process. While standing on any branch, you can use:

python manage.py unmigrate master

Or if it’s going to be master anyways, this will suffice:

python manage.py unmigrate

And that’s it!

python manage.py unmigrate HEAD~12
python manage.py unmigrate b13553d
python manage.py unmigrate v1.33.7

python manage.py unmigrate --dry-run

python manage.py unmigrate --fake
python manage.py migrate --fake