Merge pull request github#24044 from github/repo-sync

repo sync

Author: Octomerger

content/actions/using-github-hosted-runners/using-larger-runners.md

@@ -98,7 +98,13 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
 
 ## Running jobs on your runner
 
-Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. You can use runner groups or labels to define where your jobs run. 
+Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. You can use runner groups or labels to define where your jobs run.
+
+{% note %}
+
+**Note:** When you add a {% data variables.actions.hosted_runner %}, it is automatically assigned default labels that correspond to the runner name and its operating system. You cannot add custom labels to {% data variables.actions.hosted_runner %}s, but you can use the default labels or the runner's group to send jobs to specific types of runners.
+
+{% endnote %}
 
 Only owner or administrator accounts can see the runner settings. Non-administrative users can contact the organization administrator to find out which runners are enabled. Your organization administrator can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
 
@@ -130,28 +136,6 @@ jobs:
 
 {% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
 
-### Using multiple labels
-
-You can specify multiple labels that need to be matched for a job to run on a runner. A runner will need to match all labels to be eligible to run the job.
-
-In this example, a runner will need to match all three of the labels to run the job:
-
-```yaml
-name: learn-github-actions
-on: [push]
-jobs:
-  check-bats-version:
-    runs-on:
-      labels: [ ubuntu-20.04-16core, gpu, qa ]
-    steps:
-      - uses: {% data reusables.actions.action-checkout %}
-      - uses: {% data reusables.actions.action-setup-node %}
-        with:
-          node-version: '14'
-      - run: npm install -g bats
-      - run: bats -v
-```
-
 {% data reusables.actions.section-using-unique-names-for-runner-groups %}
 
 ## Managing access to your runners

data/reusables/actions/add-hosted-runner-overview.md

@@ -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 runner creation process. In addition, you can modify the runner's group membership after you've registered the runner. For more information, see "[AUTOTITLE](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
+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 "[AUTOTITLE](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."