Clarify runner usage for GitHub Enterprise Server users#44019
Clarify runner usage for GitHub Enterprise Server users#44019Sharra-writes merged 3 commits intogithub:mainfrom
Conversation
Added note about GitHub Enterprise Server users needing to use self-hosted runners instead of GitHub-hosted runners.
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 comment was marked as spam.
This comment was marked as spam.
2 similar comments
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Co-authored-by: Sharra-writes <sharra-writes@github.com>
|
@mcummings128 This is fine. We have a reusable for it, though, so I just substituted that in. I'll get this approved. |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
|
Thank you!! |
Added note about GitHub Enterprise Server users needing to use self-hosted runners instead of GitHub-hosted runners.
Why:
Closes: Issue #44020
What's being changed (if available, include any code snippets, screenshots, or gifs):
Adds note regarding that GHES instances cannot use Github-hosted runners. This is mentioned in the How-tos: Manage runners: Github-hosted runners documentation, and should be mentioned here for conformity and another way to inform potential users of GHES that Github-hosted runners cannot be used
Check off the following: