Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to force rebase_migration to rebase even if the migration has been applied #184

Closed
ktowen opened this issue Jun 13, 2022 · 2 comments · May be fixed by #346
Closed

Option to force rebase_migration to rebase even if the migration has been applied #184

ktowen opened this issue Jun 13, 2022 · 2 comments · May be fixed by #346

Comments

@ktowen
Copy link

ktowen commented Jun 13, 2022

Description

I don't want to stop the rebase to unapply that migration, I would prefer to rebase the migration anyways and do migrate --fake if needed

@adamchainz
Copy link
Owner

Sure, if you want to contribute such an option, feel free.

@adamchainz
Copy link
Owner

Closing due to inactivity and lack of further demand.

roanster007 added a commit to roanster007/django-linear-migrations that referenced this issue Aug 5, 2024
…re applied.

Previously, while rebasing migrations, if the migration to be
rebased is already applied, it would throw out an error asking
to un apply the migration before rebasing.

This commit un applies the migrations and rebases them when
the migrations to be rebased are already applied. This is done
by first creating a --merge migration, un applying the previous
migrations, removing the --merge migration, and then rebasing
the existing migrations.

Fixes adamchainz#184
roanster007 added a commit to roanster007/django-linear-migrations that referenced this issue Aug 9, 2024
Previously, while rebasing migrations, if the migration to be
rebased is already applied, it would throw out an error asking
to un apply the migration before rebasing.

This commit un applies the migrations and rebases them when
the migrations to be rebased are already applied. This is done
by first creating a --merge migration, un applying the previous
migrations, removing the --merge migration, and then rebasing
the existing migrations.

Fixes adamchainz#184
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants