What needs to be done to ensure that only specific repositories can access the runners in an organization runner group?

Question

Options

• AUse GitHub's meta API to configure access.
• BAdd a label to the runner group.
• CConfigure repository access in the runner group settings.
• DConfigure the Actions Policies to "Only selected repositories".

• A
  4% (1)
• B
  8% (2)
• C
  84% (21)
• D
  4% (1)

Explanation

Configuring repository access directly within the runner group settings (option C) is the correct approach because GitHub provides a dedicated UI in the organization's runner group settings where you can restrict which repositories are allowed to use the group - this is the intended, purpose-built mechanism for this control. Option A is wrong because the meta API exposes GitHub IP ranges and system info, not runner group access controls. Option B is wrong because labels on runner groups are used by workflows to target a runner group, not to restrict which repositories can use it. Option D is wrong because "Only selected repositories" under Actions Policies controls which repositories can use Actions at all, not which ones can access a specific runner group.

Memory tip: Think "group settings control group access" - if you want to restrict who gets into a runner group, you manage that from inside the runner group's own settings page, just like a club's membership list lives with the club, not on a sign outside.

No community discussion yet for this question.