jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-26 14:02:45 -05:00
Code Issues Projects Releases Wiki Activity

Updated larger runner doc for non-admin users (#21065)

Browse Source 
Co-authored-by: Dimitrios Philliou  <d1m1tr10s@github.com>
This commit is contained in:
Lucas Costi
2022-10-04 11:25:31 +10:00
committed by GitHub
parent 6d0df0b0da
commit 321f93bd45
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/actions/using-github-hosted-runners/using-larger-runners.md
View File

@@ -87,7 +87,7 @@ You can add a {% data variables.actions.hosted_runner %} to an organization, whe
## Running jobs on your runner
Once your runner type has been been defined, you can update your workflows to send jobs to the runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. In this example, a runner group is populated with Ubuntu 16-core runners, which have been assigned the label `ubuntu-20.04-16core`. If you have a runner matching this label, the `check-bats-version` job then uses the `runs-on` key to target that runner whenever the job is run:
```yaml
name: learn-github-actions
@@ -104,6 +104,8 @@ jobs:
- run: bats -v
```
To find out which runners are enabled for your repository and organization, you must contact your organization admin. Your organization admin can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
## Managing access to your runners
{% note %}