Repository navigation
feat(ci)!: retire the unused lint workflow - #738
Conversation
Retain the live Go pipeline, both signing assertions, scanner and credential controls after the final production consumer migrated. BREAKING CHANGE: the whole-repository lint workflow is no longer exported. Existing immutable pins remain available; consuming repositories own this single-product job. Refs #731.
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
@coderabbitai full review |
✅ Action performed
|
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Docstring Coverage |  |
Docstring coverage is 54.55% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 11 functions across 16 files. (5 skipped:… | Write docstrings for the functions missing them to satisfy the coverage threshold. |
-
Check name Status Explanation Title check The title clearly identifies the main change: retiring the unused Lint workflow. It is concise and specific. Description check The description explains why the workflow is retired, what changes, the preserved controls, and the breaking-change impact. It is directly related to the changeset. Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 54.55% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 11 functions across 16 files. (5 skipped: 5 unsupported.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Comment @coderabbitai help to get the list of available commands.
Readiness at Full native CI 40119411502 passes at this exact head, including catalogue parity and retained production scanner controls. CodeRabbit completed a full review of this commit with no actionable findings; complete thread and formal-review reads are clear. I opened the rendered README at this commit, expanded both matching Reference/Purpose/Source indexes and one workflow reference, and verified the independent collapsibles work. The export being removed has no remaining consumer runtime to exercise; retained behavior is covered by the native controls. The breaking release, signed publication and final source/reconciliation audit remain tracked on #731 after this source merge. |
Why
The last product now owns its whole-repository lint job, so the shared wrapper and its dedicated smoke fixtures no longer serve a production consumer. Keeping them adds maintenance work and obscures ownership.
What
Retire the unused interface and document the remaining catalogue consistently. Preserve the live Go validation, both signing assertions, credential isolation, scanner cases and manual-fix coverage.
Part of #731
💥 Breaking change: the legacy whole-repository Lint interface is removed from the next major release. Existing immutable release pins remain available.