chore(ci): remove dead Codecov upload steps + lock pins - #86
Conversation
Line-exact removal of dead-app CI references.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe CI test job no longer uploads ChangesCI coverage handling
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the Codecov removal and gives useful implementation context. However, it omits most required template sections, including Type of Change, Related Issues, Testing, Checklists, Performance Impact, Breaking Changes, and Reviewer Checklist. Resolution Update the description to follow the repository template. Include the relevant change type, issue reference or an explicit no-issue statement, testing performed and results, checklist status, performance impact, breaking-change assessment, security and compliance confirmations, and any applicable screenshots or output.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the test run bright Comment |
|



Removed CI references to apps that are no longer installed on this account/org.
Why this is a fix, not a tidy-up
codecov/codecov-action@*(standards/config/settings/actions-allowlist.json->pruned_from_live_2026_09_02), so a workflow still calling it fails at job start instead of quietly no-op-ing.standardsspec §9, rulings R1/R4/R5).Changes
.github/workflows/ci.yml— appliedNotes
actions.lockentries for the removed actions are deleted in this same commit (the same-PR regen rule in the CI/CD regularisation spec §6.4), soactions-lock-verifysees no drift.gitar-approvedlabel is intentionally frozen perdocs/LABELS.adoc— it is not an active Gitar install, so it stays.