Reenable codecov status#2367
Conversation
Greptile SummaryThis PR re-enables Codecov project and patch status checks (previously set to
Confidence Score: 5/5Both files are CI/config-only changes with no production code impact; the workflow follows least-privilege principles and handles the label-removal 404 edge case correctly. The codecov change is a straightforward config toggle. The label workflow correctly gates on No files require special attention. Both changed files are CI configuration with limited blast radius. Important Files Changed
Sequence DiagramsequenceDiagram
participant Dev as Developer
participant GH as GitHub
participant CI as CI Workflow
participant LW as pr-label Workflow
participant Codecov
Dev->>GH: Push commit / Open PR
GH->>LW: pull_request_target (synchronize/opened)
LW->>GH: checks.listForRef(ci-complete, sha)
GH-->>LW: [] (not run yet)
LW->>GH: removeLabel(ready-to-merge) → 404 caught, OK
GH->>CI: Trigger ci.yml
CI->>Codecov: Upload coverage report
Codecov-->>GH: Post project/patch status check
CI->>GH: ci-complete job finishes
GH->>LW: check_run completed (ci-complete)
LW->>GH: listPullRequestsAssociatedWithCommit(sha)
GH-->>LW: "[PR #N]"
LW->>GH: checks.listForRef(ci-complete, sha)
GH-->>LW: "[{conclusion: success}]"
LW->>GH: addLabels(ready-to-merge)
Reviews (4): Last reviewed commit: "Comment layout" | Re-trigger Greptile |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
I think we need these status checks so people are more aware when coverage drops.
This also adds a workflow to add a label to PRs that have all required checks passing, so it's easy to see which PRs are mergeable. This also means it can be used in a custom view to filter out PRs which are not ready.