Repository navigation
Conversation
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 |
At signed head The full rendered-property/reconciler suite, generated-source parity, executable two-repository selector fixture, workflow boundary assertions, Go vet and whitespace checks pass locally. Hosted CI is still pending. Deployment remains held for the requested maintainer approval of the dedicated verification selection; no installation grants have changed. The previous native rollout 40436385072 initialized assignments but correctly refused retirement after incomplete readback. Independent native inspection now confirms all 26 declared repositories have the four desired values plus the retained documentation value, all 104 managed assignments are Ready/Synced, and the Go template's previously observed missing-property warning is absent. This does not clear the incomplete workflow or the final four-property acceptance gate. |
@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. More of your lovely PRs please. 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". |
At This stays a draft on the maintainer authorization requested through the private native channel. The complete-portfolio readback and final four-property deployment acceptance remain pending; neither the green source review nor independently observed repository values substitutes for that live workflow proof. |
Why
The property rollout cannot finish because its verification view omits declared repositories. It correctly keeps the old property until the complete portfolio can be verified.
What
Separate portfolio verification from configuration changes, so every declared repository can be checked without extending the writer's reach. Keep incomplete results as a deployment blocker and require approval for the verification selection.
Part of #773