1
0
mirror of synced 2025-12-19 18:10:59 -05:00

Added updates from pairing

This commit is contained in:
Martin Lopes
2022-09-01 15:28:04 +10:00
parent 224d8599a9
commit 8f646ec122
7 changed files with 15 additions and 17 deletions

View File

@@ -21,15 +21,17 @@ shortTitle: Using runner groups
{% ifversion ghec or ghes or ghae %}
## Creating a runner group for an organization
## Creating a self-hosted runner group for an organization
{%- ifversion ghec or ghes %}
{%- ifversion ghes %}
{% data reusables.actions.self-hosted-runner-security-admonition %}
{%- endif %}
{% data reusables.actions.creating-a-runner-group-for-an-organization %}
## Creating a runner group for an enterprise
## Creating a self-hosted runner group for an enterprise
{%- ifversion ghec or ghes %}
@@ -41,7 +43,7 @@ shortTitle: Using runner groups
{% endif %}
## Changing the access policy of a runner group
## Changing the access policy of a self-hosted runner group
{%- ifversion fpt or ghec or ghes %}
@@ -56,15 +58,15 @@ shortTitle: Using runner groups
{% data reusables.actions.changing-the-name-of-a-runner-group %}
{% ifversion ghec or ghes or ghae %}
## Automatically adding a runner to a group
## Automatically adding a self-hosted runner to a group
{% data reusables.actions.automatically-adding-a-runner-to-a-group %}
## Moving a runner to a group
## Moving a self-hosted runner to a group
{% data reusables.actions.moving-a-runner-to-a-group %}
## Removing a runner group
## Removing a self-hosted runner group
{% data reusables.actions.removing-a-runner-group %}

View File

@@ -1,13 +1,13 @@
---
title: Controlling access to larger runners
intro: You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.
product: '{% data reusables.gated-features.hosted-runners %}'
versions:
feature: 'actions-hosted-runners'
type: tutorial
shortTitle: Controlling access to {% data variables.actions.hosted_runner %}s
---
{% data reusables.actions.hosted-runners-beta %}
{% data reusables.actions.enterprise-beta %}
{% data reusables.actions.enterprise-github-hosted-runners %}

View File

@@ -2,16 +2,15 @@
title: Using larger runners
intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
miniTocMaxHeadingLevel: 3
product: '{% data reusables.gated-features.hosted-runners %}'
versions:
feature: 'actions-hosted-runners'
shortTitle: Using {% data variables.actions.hosted_runner %}s
---
{% data reusables.actions.hosted-runners-beta %}
## Overview of {% data variables.actions.hosted_runner %}s
In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} also offers a Enterprise and Team plan customers a range of {% data variables.actions.hosted_runner %}s with more RAM and CPU. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} also offers {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_team %} plan customers a range of {% data variables.actions.hosted_runner %}s with more RAM and CPU. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
When you add a {% data variables.actions.hosted_runner %} to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. {% data variables.product.prodname_dotcom %} will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define.

View File

@@ -1,4 +1,5 @@
# Reference: #6458
# Larger GitHub-hosted runners
versions:
fpt: '*'
ghec: '*'

View File

@@ -1,3 +1,3 @@
You can choose an operating system and a hardware configuration from the list of available options. When new instances of this runner are deployed through autoscaling, they'll use the same operating system and hardware configuration you've defined here.
You can also define the labels that identify the runner, which is how your workflows will be able to send jobs to the runners for processing (using `runs-on`). New runners are automatically assigned to the default group, or you can choose which group the runners must join during the creation process. In addition, you can modify the runner's group membership after you've registered the runner. For more information, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
You can also define the labels that identify the runner, which is how your workflows will be able to send jobs to the runners for processing (using `runs-on`). New runners are automatically assigned to the default group, or you can choose which group the runners must join during the runner creation process. In addition, you can modify the runner's group membership after you've registered the runner. For more information, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."

View File

@@ -1,5 +0,0 @@
{% note %}
**Note**: The {% data variables.actions.hosted_runner %} feature is currently in beta and subject to change.
{% endnote %}

View File

@@ -0,0 +1 @@
The {% data variables.actions.hosted_runner %}s feature is currently in beta for organizations and enterprises using the {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %} plans, and is subject to change.