Repository navigation
ci: remove redundant CI caller rollups - #13558
teamleaderleo wants to merge 6 commits into
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe CI workflow removes ChangesCI route validation
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Refactor Sequence Diagram(s)sequenceDiagram
participant CheapAggregates
participant RoutedJobs
participant macos
participant ci-status
CheapAggregates->>macos: provide aggregate results and route outputs
macos->>macos: apply route-aware admission conditions
RoutedJobs->>ci-status: provide routed job results
macos->>ci-status: provide macOS result
ci-status->>ci-status: validate routes and required results
Merge Risk: ⚪ Minimal · up to The change removes redundant CI rollups while preserving route-aware admission and validation, with coverage for routed and unrouted work. No merge-blocking production risk is identified. 🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (24 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 18 functions across 1 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
All contributors have signed the CLA ✍️ ✅ |
|
Superseded by #13578, rebuilt directly from current |
Summary
Remove the two caller-level Linux rollups that only re-check results already owned elsewhere:
linux-preflight;testsaggregate;ci-statusthe single final owner of caller route/result consistency.Why
Current CI already starts macOS after
changes+static-preflight, independently of the longer guard/web lanes. The remaining caller flow still allocates two extra Linux runners solely to reinterpret results:Reusable workflows already publish authoritative aggregate checks:
guard-statusvalidates the routed guard children;web-statusvalidates routed web/macOS/agent-session inputs and subareas;The final required
ci-statuscan therefore enforce the caller-level route/result contract directly, without two scheduling hops.Result semantics
ci-statusnow requires:changesandstatic-preflightto succeed;macOS admission itself stays exactly on the current
changes+static-preflightgate, preserving overlap with routed Linux checks.Effect
Two Linux runner allocations and two caller scheduling hops disappear from every relevant CI run, while the required check remains
ci-status.Testing
Regression coverage now pins:
ci-status.Demo Video
N/A — CI control-plane cleanup only.
Review Trigger
Checklist
ci-status