Administrators placed production self-hosted runners in a runner group named 'prod-runners' visible to selected repositories. How should a workflow job request a runner from that group?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Use runs-on.group (and optional labels) to target an organization/enterprise runner group. Environments and permissions keys are different concepts.
Full explanation below image
Full Explanation
Runner groups control which repositories can use which runners. Jobs target them with the mapping form of runs-on including group and optional labels for further filtering. deployment environments gate secrets and protection rules but are not runner group selectors. permissions configures token scopes. container defines the job's container image. If a repository is not allowed in the group, the job queues indefinitely or fails to match—admins must grant access. Combine groups with labels for GPU vs CPU pools inside production.