jobs.<job_id>.runs-on to define the type of machine to run the job on.
The destination machine can be a self-hosted runner.
You can target runners based on the labels assigned to them.
You can provide
runs-onas a single string or as an array of strings.
If you specify an array of strings, your workflow will execute on any runner that matches all of the specified
If you would like to run your workflow on multiple machines, use
To specify a self-hosted runner for your job, configure
runs-on in your workflow file with self-hosted runner labels.
All self-hosted runners have the
self-hosted label. Using only this label will select any self-hosted runner. To select runners that meet certain criteria, such as operating system or architecture, we recommend providing an array of labels that begins with
self-hosted (this must be listed first) and then includes additional labels as needed. When you specify an array of labels, jobs will be queued on runners that have all the labels that you specify.
self-hosted label is not required, we strongly recommend specifying it when using self-hosted runners to ensure that your job does not unintentionally specify any current or future GitHub-hosted runners.
runs-on: [self-hosted, linux]