Repository navigation
fix(rulesets): let the next Platform merge group validate early - #893
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 cleared 2026-11-11: devantler-tech/platform#6036 merged at 07:05Z, and the first merge group built on it (platform#6037, run 42977006972) deployed and succeeded at 07:2xZ, so production keeps deploying in queue order. |
Readiness at
Promoting. After it reconciles, the Platform queue should start the second entry's checks while the first is still validating. |
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