ci: add runner input to repo-standards reusable (default hosted) - #60
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: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe reusable ChangesStandards workflow runner
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Merge Risk: ⚪ Minimal · up to Existing standards checks retain their runner selection. The change is ready to merge after normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 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 |
Adds a
runnerinput to the reusablerepo-standardsworkflow, defaulting toubuntu-latestso every existing caller keeps its current behaviour. Callers opt in by passingrunner: ${{ vars.USE_SELF_HOSTED == 'true' && 'self-hosted' || 'ubuntu-latest' }}, mirroringsecurity-scan.yml.Follow-up (blocked on this merge): point the calling repos' repo-standards jobs at the switch (bump its pin to the merged SHA + pass the input). Passing the input against the old pin would error until this lands.
Summary by CodeRabbit