#36620: Automate test coverage check on pull requests
--------------------------------------+------------------------------------
Reporter: Jacob Walls | Owner: Saurabh
Type: Cleanup/optimization | Status: closed
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: => fixed
* status: new => closed
Comment:
In [changeset:"26b0e2bb92caf2d16cabe455792350f20d6f42ca" 26b0e2bb]:
{{{#!CommitTicketReference repository=""
revision="26b0e2bb92caf2d16cabe455792350f20d6f42ca"
Fixed #36620 -- Fixed workflow to summarize coverage in PRs.
Follow-up to a89183e63844a937aacd3ddb73c4952ef869d2cc, which was
reverted in e4c4a178aa642f8493b7ae2c0ad58527af51f67e because a change
to the workflow trigger resulted in the PR branch not being checked out.
We used this opportunity to reimplement the coverage tracing and coverage
commenting in a two-workflow pattern with more granular permissions.
To reduce duplicative workflows, we removed the existing python test
workflow
on PRs, at least until we run more distinct configurations on GitHub
actions. The
run with coverage tracing enabled is sufficient for now. The existing
workflow still
runs on pushes to main. We can revisit when adding more test
configurations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36620#comment:12>
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/0107019ae9f7da2e-9f5cf43e-c333-41f9-8c22-ca4c547c4225-000000%40eu-central-1.amazonses.com.
