Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/manage-access
What part(s) of the article would you like to see updated?
The article covers moving a runner into a custom runner group, but doesn't mention a behavior several users have independently run into: after moving an org-level self-hosted runner from the Default group into a custom group, the runner stops appearing on the repository's Settings → Actions → Runners page — even when the group has "All repositories" access configured correctly.
The runner continues to route and execute jobs normally; it only disappears from that specific settings view. It still shows up correctly on the newer Actions → Management → Runners page.
It would help to add a short note under "Moving a self-hosted runner to a group" (or wherever fits best) clarifying that repository-level visibility on the legacy Settings page may not reflect custom group membership, so people don't assume their runner group permissions are misconfigured.
Additional information
Reliably reproducible - confirmed independently by at least three people with different organizations, using different custom runner group configurations (see thread below). One user explicitly tested and confirmed the runner still picks up runs-on: self-hosted jobs despite not appearing in the Settings UI, which points to this being a display-only gap rather than an access/permissions issue.
Community discussion with full repro steps and screenshots: https://github.com/orgs/community/discussions/201615
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/manage-access
What part(s) of the article would you like to see updated?
The article covers moving a runner into a custom runner group, but doesn't mention a behavior several users have independently run into: after moving an org-level self-hosted runner from the Default group into a custom group, the runner stops appearing on the repository's Settings → Actions → Runners page — even when the group has "All repositories" access configured correctly.
The runner continues to route and execute jobs normally; it only disappears from that specific settings view. It still shows up correctly on the newer Actions → Management → Runners page.
It would help to add a short note under "Moving a self-hosted runner to a group" (or wherever fits best) clarifying that repository-level visibility on the legacy Settings page may not reflect custom group membership, so people don't assume their runner group permissions are misconfigured.
Additional information
Reliably reproducible - confirmed independently by at least three people with different organizations, using different custom runner group configurations (see thread below). One user explicitly tested and confirmed the runner still picks up runs-on: self-hosted jobs despite not appearing in the Settings UI, which points to this being a display-only gap rather than an access/permissions issue.
Community discussion with full repro steps and screenshots: https://github.com/orgs/community/discussions/201615