From e8f0efe6d9d09228cd9074080b6898604c2d02d7 Mon Sep 17 00:00:00 2001 From: stefansli <104021830+stefansli@users.noreply.github.com> Date: Thu, 15 Feb 2024 01:30:31 +0100 Subject: [PATCH] Fix typo in section-choosing-the-runner-for-a-job.md (#31638) Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com> --- .../actions/jobs/section-choosing-the-runner-for-a-job.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index e414ff8015..a2ff3af204 100644 --- a/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -8,7 +8,7 @@ Use `jobs..runs-on` to define the type of machine to run the job on. - a single string - a single variable containing a string - an array of strings, variables containing strings, or a combination of both - - a `key: value` pair using the `group` or `label` keys + - a `key: value` pair using the `group` or `labels` keys - If you specify an array of strings or variables, your workflow will execute on any runner that matches all of the specified `runs-on` values. For example, here the job will only run on a self-hosted runner that has the labels `linux`, `x64`, and `gpu`: ```yaml