Your organization enabled GitHub-hosted larger runners for heavy builds. How do jobs typically select a larger runner?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Admins define larger runners with labels or groups; workflows opt in via runs-on. Timeouts, permissions blocks, and matrix size do not auto-upgrade hardware.
Full explanation below image
Full Explanation
GitHub-hosted larger runners (and similar premium runner offerings) are provisioned at the org/enterprise level with specific names/labels and often restricted by runner groups. Workflow authors set runs-on accordingly. They consume different billing multipliers/minutes than standard 2-core runners. timeout-minutes only limits duration. The permissions key controls GITHUB_TOKEN scopes, not machine size. Matrix width does not change runner SKU. Teams should document which labels mean 4-core vs 16-core so authors do not overspend.