[Django] #22031: Checks framework complains about unapplied migrations when running `manage.py migrate`

[Django]

#22031: Checks framework complains about unapplied migrations when running
`manage.py migrate`
---------------------------------------+------------------------
Reporter: bmispelon | Owner:
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+------------------------
Suppose you've created a new application with some models and you've
subsequently run `manage.py makemigrations`.

The next step is to run `manage.py migrate`.

When you do that, the first thing that you see is the checks framework
telling you that you have unapplied migrations and that you should run
`manage.py migrate`.

That doesn't seem very helpful and I think it'd be better in this case to
not output anything.

--
Ticket URL: <https://code.djangoproject.com/ticket/22031>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#22031: Checks framework complains about unapplied migrations when running
`manage.py migrate`

-----------------------------+--------------------------------------
Reporter: bmispelon | Owner:
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-----------------------------+--------------------------------------
Changes (by mjtamlyn):

* status: new => closed
* resolution: => duplicate

Comment:

This is effectively a duplicate of #21856 - this warning should not be
part of the checks framework.

--
Ticket URL: <https://code.djangoproject.com/ticket/22031#comment:1>