docs: propose note about custom runner group UI visibility#45134
Draft
DhruvalAnandkar wants to merge 1 commit into
Draft
docs: propose note about custom runner group UI visibility#45134DhruvalAnandkar wants to merge 1 commit into
DhruvalAnandkar wants to merge 1 commit into
Conversation
Adds a note clarifying that organization runners in custom groups may not render in legacy repository settings, despite retaining full routing access, to prevent user confusion.
github-actions
Bot
added
the
triage
Contributor
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a note clarifying that organization runners in custom groups may not render in legacy repository settings, despite retaining full routing access, to prevent user confusion.
Draft — Proposing this note pending confirmation on Issue #45132. Leaving this as a draft and open to wording changes from the docs team once the behavior is reviewed.
Why:
Several users independently reported in a Community Discussion that org-level runners assigned to custom runner groups stop appearing on the legacy repository Settings > Actions > Runners page — even with correct repository access configured — while continuing to route and execute jobs normally. This note aims to prevent users from assuming their runner group permissions are misconfigured.
Related discussion: https://github.com/orgs/community/discussions/201615
Related issue: #45132
Closes: N/A — not intended to auto-close; see related issue above
What's being changed (if available, include any code snippets, screenshots, or gifs):
Adds a {% note %} callout under "Changing which repositories can access a runner group" in content/actions/how-tos/manage-runners/self-hosted-runners/manage-access.md.
Check off the following: