GitHub Actions Runner Group Has No Access to the Repository

An org-level self-hosted or larger runner exists with matching labels, but the runner group is not configured to allow this repository, so no runner is eligible and the job waits or fails.

What this error means

A job targeting an org runner stays queued or fails to find a runner, even though a runner with the right labels is online - because the repository is outside the runner group access list.

Requested labels: self-hosted, build-fleet
Waiting for a runner to pick up this job...
# the build-fleet runner group does not grant this repo access

Common causes

Repository not granted in the runner group

Org runner groups restrict which repositories can use them. A repo not in the group access list cannot schedule jobs on those runners.

Group limited to selected workflows or visibility

Some groups only allow public repos, or only specific workflows. A private repo or non-listed workflow is then ineligible.

How to fix it

Grant the repository access to the group

1. In org settings, open Actions runner groups and select the group.
2. Add the repository (or set the group to all repositories) under repository access.
3. Confirm any workflow or visibility restrictions also allow this run.

Target a group the repo can use

Use labels that resolve to a runner group this repository is allowed to access, or the default group.

runs-on: [self-hosted, build-fleet]   # ensure build-fleet group allows this repo

How to prevent it

• Keep runner group repository access in sync with the teams using them.
• Document which labels map to which runner groups.
• Audit group visibility and workflow restrictions when onboarding repos.

Related guides