From 5230e774dd71a702f3ccfeed12ada41d4e3e5ade Mon Sep 17 00:00:00 2001 From: stefansli <104021830+stefansli@users.noreply.github.com> Date: Wed, 14 Feb 2024 09:41:27 +0100 Subject: [PATCH] Fix typo in section-choosing-the-runner-for-a-job.md --- .../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 e414ff801560..a2ff3af2046f 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