From 9bc1671fb941da8e5a128c3e0263a78cd2360c4b Mon Sep 17 00:00:00 2001 From: Steven Lariscy Date: Thu, 17 Aug 2023 04:18:43 -0400 Subject: [PATCH] Update section-choosing-the-runner-for-a-job.md (#27493) --- .../actions/jobs/section-choosing-the-runner-for-a-job.md | 1 + 1 file changed, 1 insertion(+) 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 5c298dbfe5..ae6717edba 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,6 +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 - 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