Repository navigation
fix(coverage): finish legacy Actions retirement - #728
Conversation
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
View coverage of the 1 most impacted file.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
The deletion and independent absence evidence are recorded on #240. This follow-up changes no managed resource or credential boundary. TDD: the post-deletion clean census fixture first failed on the obsolete Actions exemption. After removing it, the actual coverage client passes its complete stable paginated installation controls, while recreated Actions, unseen repositories, incomplete reads, changed installation metadata and a synthetic stale exception still fail for their intended reasons. The extra pagination fixture is an explicitly archived synthetic repository, not a hidden production exception. All 15 repository Maintenance baseline commands pass, including rendered withdrawal and complete coverage. Instruction layout passes its 20 negative controls; README interface parity passes all 43 behavioral cases; ShellCheck with source following and diff checks pass. Both action/workflow indexes retain the same parallel collapsible structure and all existing interfaces. Fresh native CI, current-head substantive review, protected merge and the normal reviewed-main live governance audit remain required. No historic signer identity or archived evidence is rewritten. |
Review hand-off at This is the final post-deletion correction, not a deletion request. Verified authenticated absence and recovery evidence are linked from #240. The temporary exception is removed; the complete actual-client controls still reject unseen or recreated repositories, partial/unstable inventory, inappropriate installation metadata and a synthetic stale exception. Documentation reflects the maintained catalogue and preserves historical identity data. No managed resource or credential grant changes. |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep them coming! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Ready at signed head All 15 local baseline commands, complete coverage-client controls, 43 README parity cases, 20 instruction-layout mutations, ShellCheck with source following and diff checks pass. The post-deletion clean fixture first failed on the stale exemption. Recreated Actions, unseen repositories, unstable/partial reads and a synthetic stale exception remain blocking; no managed resource, credential boundary, historical identity or required check is removed. Repository deletion, positive authentication controls, complete organization absence and the verified private recovery backup are recorded on #240. Actions and reusable-workflow references retain the same parallel indexes and collapsibles. Promotion will retain any new native checks; protected merge, normal postmerge validation and the reviewed-main live governance audit remain required before final delivery is recorded. |
Why
The retired automation repository has now been deleted after its consumers and protection were migrated. Its temporary exemption would make the next governance audit fail and could conceal an accidental recreation.
What
Remove the obsolete exception while retaining complete-coverage and failure checks. Update the catalogue and contributor guidance to identify the maintained automation and preserve historical verification and recovery context.
Fixes #240