Repository navigation
test: pin persistent control-plane guard groups - #13609
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
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; 3 remain after this review. 📝 WalkthroughWalkthroughThe change adds workflow ownership mappings for build graph health tooling and updates persistent macOS routing tests to verify both guard outputs and routed Linux test groups. ChangesCI guard updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to This updates CI guard ownership and validates routing behavior without an identified production or merge-blocking risk. 🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (24 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
|
Latest current-head proof: |
The Linux guard router kept a hand-written copy of every workflow-guard-tests step (STEP_OWNERS) and every path those steps run (PATH_OWNERS), and a test required the copy to equal the workflow. Two PRs that each passed alone could land a copy that disagreed with the workflow: #13535 added "Validate build graph health tooling" while #13585 introduced the copy, and every PR failed guards until #13609. Ownership now comes from the workflow. Each step's `if: ${{ matrix.group == '<group>' }}` names its group and each path its `run:` executes belongs to that group. The router reads ci-guards.yml with a small line scanner, because the changes job runs on bare python3 without PyYAML; a test holds the scanner to yaml.safe_load field by field. An unreadable workflow fails open to every group. STEP_OWNERS is gone, and PATH_OWNERS keeps only the 24 indirect inputs (imported scripts, the agent-chat working directory, the ghostty submodule, skill files). Routing is unchanged for every path the old tables knew. A step with an unknown group fails its own PR with the exact file to edit. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
#13607 landed the production ownership repair that originally motivated this PR.
This branch now keeps only the useful follow-up regression: assert the exact
workflow-guard-testsgroups selected for persistent-Mac/build-health control-plane inputs.The existing test already checks that these paths select the outer Linux guard lane. This tightens it to prevent accidental fan-out inside that lane:
preflight;preflight + quality-determinism.No production routing or ownership data changes remain in this PR.