#34632: Let makemigrations output an error message with --check
-------------------------------------+-------------------------------------
Reporter: Jakob Probst | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: wontfix
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 Mariusz Felisiak):
* cc: Jacob Walls (added)
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for the report (partly related with #34436), however, this is a
documented and intended change.
> Furthermore if the command is run in a pipeline it is not possible to
know for certain if the command failed because of a wrongly set up
pipeline job or if a migration is actually missing.
You can always check a status code. I don't think outputting an error
message will improve it somehow.
Please first start a discussion on the DevelopersMailingList, where you'll
reach a wider audience and see what other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow the triaging guidelines with regards to
wontfix tickets].
--
Ticket URL: <https://code.djangoproject.com/ticket/34632#comment:1>
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/010701888b17d39c-74344278-4127-4599-a17a-0799a1b76ae8-000000%40eu-central-1.amazonses.com.
