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
34051	makemigrations --check generating migrations is inconsistent with other uses of --check	Jacob Walls	Jacob Walls	"To script a check for missing migrations but without actually intending to create the migrations, it is necessary to use both `--check` and `--dry-run`, which is inconsistent with `migrate --check` and `optimizemigration --check`, which just exit (after possibly logging a bit).

I'm suggesting that `makemigrations --check` should just exit without making migrations.

The choice to write the migrations anyway was not discussed AFAICT on ticket:25604 or https://groups.google.com/g/django-developers/c/zczdY6c9KSg/m/ZXCXQsGDDAAJ.

Noticed when reading [https://github.com/django/django/pull/15845#issue-1305277307 PR to adjust the documentation of migrate --check]. I think the current documentation is silent on this question."	Cleanup/optimization	closed	Migrations	dev	Normal	fixed			Ready for checkin	1	0	0	0	0	0