id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36643	Migrate should not check for consistent history when faking migrations	Alexandru Chirila		"If for some reason or another you end up needing to fake apply a migration, it will still run the `check_consistent_history`.

So if you ended up by accident (or on purpose somehow?) with a invalid migration history, there is no way of fixing it except manually doing things in the `django_migrations` table. 

It seems like a scenario like this ought to be fixable using the ""fake"" apply of migrations, but as far as I can tell there is no way of doing that as the check will always fell and throw an error, so the fake aplication can never be done.

{{{
.venv/lib/python3.12/site-packages/django/db/migrations/loader.py"", line 327, in check_consistent_history
    raise InconsistentMigrationHistory(
django.db.migrations.exceptions.InconsistentMigrationHistory: Migration shortner.0001_initial is applied before its dependency charts.0001_initial on database 'default'.
}}}"	New feature	closed	Migrations	5.2	Normal	wontfix		Alexandru Chirila	Unreviewed	0	0	0	0	0	0