rebase_migration behaviour when renaming an applied migration

[adamchainz]

As suggested by @tolomea.

Before renaming the migration, rebase-migration could roll it back from the local DB, perhaps with a prompt, or it could simply warn/error that the migration has already been applied.

[SleepyHarry]

Perhaps simply renaming entries and fiddling the applied time in the django_migrations table would be sufficient (+/- a warning/error/prompt)

[adamchainz]

That's also an option. I'd be less inclined to take it though as it wouldn't prove that the rebased migration works in its new place in the history.

[tolomea]

from my POV the minimum bar is not creating a situation where the local DB has applied migrations that no longer exist, anything beyond that is bonus

[adamchainz]

I just released version 1.3.0 with the guard added in #26 .