Repository navigation
ci: run CI on GitHub-hosted runners - #16
Conversation
Member PRs and default-branch builds ran on the private Linux runners. Route them to GitHub-hosted runners while the private runner setup is rebuilt; the reusable workflow already supports the hosted path, which non-member PRs use today. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
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: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow now sets ChangesCI runner configuration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to CI events use GitHub-hosted runners as intended. No merge-blocking risk is established by the reviewed change. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The change uses the existing hosted-runner path without increasing declared permissions or passing additional secrets. No introduced security flaw was demonstrated. Runner-specific credentials, network access, and the effective workflow version at execution remain unverified. Retained concerns Security review detailsSecurity Blast Radius
Security Findings and Attack Paths
Trust Boundaries and Controls
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
Silo Kody — review completeReview finished. Check the inline comments for findings and verify each suggestion against the code and tests. Reviewing changes in Silo
Review settingsReview OptionsThe following review options are enabled or disabled:
|
Problem
Silo's private Linux runners are being taken offline while they are rebuilt. Member PRs and default-branch builds in this repository target those runners by label, so with the runners gone those jobs would queue indefinitely. This moves them to GitHub-hosted runners.
Approach
The calling workflow passes
self_hosted: falseto the reusable workflow, so every job takes the hosted branch of itsruns-onexpression, which non-member PRs already use. The reusable workflow keeps its self-hosted support for later.Validation
actionlint passes on the changed workflow files. This PR's own CI run uses hosted runners.
AI Disclosure
🤖 Generated with Claude Code
Note
Run CI on GitHub-hosted runners
Sets the
self_hostedinput to literalfalsein ci.yml. This replaces a conditional expression that checked repository, event, actor, and branch to decide when to use self-hosted runners.Macroscope summarized 0edd043.