Repository navigation
Conversation
@codex review for ruleset ownership, single-entry merges, required checks, and guarded rollout order |
Codex Review Summary: ✅ CompletedThis 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. 👍 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". |
Code coverage overviewLanguages: C#, Go C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Blocker: devantler-tech/platform#6036 | upstream | last-verified 2026-11-11: Platform #6036 is still open in the merge queue. Keep this draft until the production deploy ordering change is merged and verified; then recheck the exact head, required checks and rollout order before promotion. |
Why
Platform pull requests can sit for hours before their merge-group checks start. The queue currently starts only one group at a time.
What
Let two groups validate at once. Each merge still contains one pull request and requires all checks.
Fixes #892