Opened 4 years ago
Closed 4 years ago
#31681 closed New feature (wontfix)
Output checks ran via manage.py checks.
| Reported by: | thenewguy | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (System checks) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
It would be helpful to have the checks framework output the checks that are run. In some situations output that can be inspected to verify a particular check was actually run is very helpful. As such, having this in CI logs is quite useful - perhaps behind a verbosity flag like the test command uses (-v 2)?
Change History (1)
comment:1 by , 4 years ago
| Component: | Uncategorized → Core (System checks) |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
| Summary: | Output checks ran via manage.py checks → Output checks ran via manage.py checks. |
| Type: | Uncategorized → New feature |
| Version: | 3.0 → master |
Note:
See TracTickets
for help on using tickets.
Thanks for this ticket, however system checks are a set of conditions checked inside many methods, that's why it will be really complicated (maybe even not feasible) to list them when running
django-admin checks. Moreoverdjango-admin checksruns all checks in selected tags so I don't think that copying a documentation page to the management command output is valuable. You can start a discussion on DevelopersMailingList if you don't agree.