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
33421	Skip consistency checks on makemigrations	Tim Nyborg	nobody	"During CI/CD, it's very useful to run `makemigrations --check --dry-run` to see if migrations have not been created for model changes.  Problem is, `makemigrations` will do migration history consitency checks on the default database, which won't exist if you're trying to make a lightweight CI stage.

You can work around this by (for example):
1. Creating a separate settings file that uses the dummy backend for `DATABASES['default']`
2. Using an env variable to switch to the dummy backend in your settings file
3. Setting up database routers which disallow migration

But these are all awkward and potentially fragile, adding logic to an application's core.

I'd suggest adding a `--skip-consistency-checks` flag which simply skips that [https://github.com/django/django/blob/0ab58c120939093fea90822f376e1866fc714d1f/django/core/management/commands/makemigrations.py#L93-L113 section]. 

If this'd be acceptable, I'd be happy to put together a pull request."	New feature	closed	Migrations	4.0	Normal	wontfix	makemigrations databases		Unreviewed	0	0	0	0	1	0