| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-03-19 | Refs #36620 -- Reduced permissions on coverage comment workflow. | Jacob Walls | |
| 2026-03-19 | Refs #36620 -- Fixed coverage comment deletion. | Jacob Walls | |
| Follow-up to 92d4aea5ffacc38c5f7903b9410d0abec83f14de. | |||
| 2026-02-12 | Refs #36620 -- Removed stray + from coverage comment workflow step. | Jacob Walls | |
| 2026-02-11 | Refs #36620 -- Shortened coverage diff comment. | Jacob Walls | |
| 2025-12-06 | Refs #36620 -- Fixed PR number extraction in coverage_comment workflow. | saurabh | |
| Passing the PR number as an artifact is more reliable in cross-fork workflows. | |||
| 2025-12-05 | Refs #36620 -- Removed PR number null check from coverage_comment workflow. | saurabh | |
| 2025-12-04 | Fixed #36620 -- Fixed workflow to summarize coverage in PRs. | saurabh | |
| 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. | |||
