From bf65d2a6f1f8963d43b963b7b8e339f02a46162a Mon Sep 17 00:00:00 2001 From: Joe Bourne Date: Thu, 28 Jan 2021 11:42:42 -0500 Subject: [PATCH] Update using-self-hosted-runners-in-a-workflow.md --- .../using-self-hosted-runners-in-a-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 9154baa567..3124b22d3d 100644 --- a/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -29,7 +29,7 @@ A self-hosted runner automatically receives certain labels when it is added to { * `self-hosted`: Default label applied to all self-hosted runners. * `linux`, `windows`, or `macOS`: Applied depending on operating system. -* `x86`, `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job: