#36620: Automate test coverage check on pull requests
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Saurabh
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"2351c1b12cc9cf82d642f769c774bc3ea0cc4006" 2351c1b1]:
{{{#!CommitTicketReference repository=""
revision="2351c1b12cc9cf82d642f769c774bc3ea0cc4006"
Refs #36620 -- Ran coverage tests workflow on forks.
We can continue to limit the coverage comment workflow to django/django,
but now that this workflow is the main python test workflow, it should
run on forks by default. The other tests workflow (currently running
only JavaScript tests) may start running python tests again once we flesh
out the matrix, but since it was duplicating the coverage tests
configuration,
we temporarily removed it.
Follow-up to 26b0e2bb92caf2d16cabe455792350f20d6f42ca.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36620#comment:18>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019beb6aae79-60e0da22-fd97-44ea-8f79-4346235902bd-000000%40eu-central-1.amazonses.com.
