ci: use cheaper ARM bootstrap runner for check-skip#7276
ci: use cheaper ARM bootstrap runner for check-skip#7276PastaPastaPasta merged 1 commit intodashpay:developfrom
Conversation
✅ No Merge Conflicts DetectedThis PR currently has no conflicts with other open PRs. |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Review GateCommit:
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe pull request updates the GitHub Actions workflow configuration in Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
Move only the
check-skipbootstrap job onto a cheaper ARM runner path.Problem
check-skipcurrently uses the generic amd64 runner setting, so even thelightweight bootstrap step can consume the more expensive primary runner pool.
Solution
RUNNER_CHECK_SKIPoverride for thecheck-skipjobubuntu-24.04-arm)This keeps the tiny bootstrap step cheap by default while still allowing an
org-level Blacksmith ARM label, such as a small 1 vCPU runner, to be
configured later without affecting the main build/test jobs.
Related
Validation
.github/workflows/build.ymlsuccessfully with PyYAML after thechange
check-skip,select_dynamic_runner.py, andcache-depends-sources.ymlupstream/develop..ci/check-skip-arm-bootstrap→ ship