#34436: `makemigrations --check` fails with error code 1 if system checks
identify
warnings
-------------------------------+--------------------------------------
Reporter: James Addison | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Mariusz Felisiak):
`check` and `makemigrations --check` are completely different commands:
- `check` is to run system checks
- `makemigrations --check` exits with a non-zero status when model changes
without migrations are detected, so the `--check` option has nothing to do
with system check.
> the 'check' for missing migrations yielded no missing migrations, so
should not return an error.
`makemigrations --check` no longer creates missing migrations files in
Django 4.2+ (see 80d38de52bb2721a7b44fce4057bcff571afc23a and #34051).
--
Ticket URL: <https://code.djangoproject.com/ticket/34436#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018717d42197-a4a2e69b-2b71-4208-9d16-7fb669a50724-000000%40eu-central-1.amazonses.com.
