Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repo sync #22406

Merged
merged 2 commits into from
Dec 1, 2022
Merged

repo sync #22406

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aae3a57
Add section for default larger runners (#33062)
lkfortuna Dec 1, 2022
96e8ae9
Merge branch 'main' into repo-sync
Octomerger Dec 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions ...ent/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,26 @@ type: tutorial

{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %}

### Default group for {% data variables.actions.hosted_runner %}s

Organizations and enterprises with access to {% data variables.actions.hosted_runner %}s will automatically receive a default runner group called "Default Larger Runners" that includes 4 runners of varying sizes. The runners in this group are pre-configured and ready for immediate use. In order to use the runners in this group, you will need to add the label corresponding to the runner of your choice to your workflow file. See the table below for labels. For more information on how to use labels, see "[Running jobs on your runner](/actions/using-github-hosted-runners/using-larger-runners#running-jobs-on-your-runner)."


#### Default Runners

|Description | Label | Image |
| ------- | ------- | ------ |
| 4-cores Ubuntu Runner | `ubuntu-latest-4-cores` | Ubuntu - Latest |
| 8-cores Ubuntu Runner | `ubuntu-latest-8-cores` | Ubuntu - Latest |
| 16-cores Ubuntu Runner | `ubuntu-latest-16-cores` | Ubuntu - Latest |
| 8-cores Windows Runner | `windows-latest-8-cores` | Windows Server - Latest |

The default {% data variables.actions.hosted_runner %} group is created at the billing entity level. If your organization is part of an enterprise account, the group will be managed on the enterprise level. If your organization does not fall under an enterprise, the group is managed on the organization level.

You will not be billed for these runners until you use them in your workflows. Once these runners are used, billing works as it normally does. For more information on billing, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners#understanding-billing)."

The default access for a {% data variables.actions.hosted_runner %} group at the enterprise level is set to automatically share with all organizations in the enterprise, but not all repositories. Organization admins will need to share the default {% data variables.actions.hosted_runner %} group with each repository separately. For {% data variables.actions.hosted_runner %} groups at the organization level, the default access is set to automatically share the group with all repositories. For more information on how to change access policies, and where to view the default {% data variables.actions.hosted_runner %} group, see "[Changing the access policy of a runner group](#changing-the-access-policy-of-a-runner-group)."

{% ifversion ghec or ghes or ghae %}

## Creating a runner group for an organization
Expand Down