self-hosted runner
A runner you install and operate on your own hardware or cloud machine, selected with the self-hosted label.
Untrusted pull request code can run inside your network and persist on the machine.
In more detail
Teams use one for special hardware or to reach systems only available inside a private network. It is not wiped between jobs, so files, caches and credentials can leak from one job to the next. Never attach one to a public repository, because a pull request from a fork could run a stranger's code on it.
Example
runs-on: [self-hosted, linux, x64]Related terms
- runner — A machine running the runner application that picks up a queued job, runs its steps and reports the result.
- runner label — A name attached to a runner that the runs-on key matches to choose where a job runs.
- fork — A copy of someone else's repository made on a hosting service such as GitHub, under your own account, so you can push to it.
- GitHub-hosted runner — A virtual machine that GitHub creates for a single job and destroys when the job ends.
Taught in
- Runners: Where Code Executes — Continuous Integration & Continuous Delivery Pipelines
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Three Kinds Of Action: JavaScript, Docker Container Or Composite — GitHub Actions (GH-200) Exam Prep
- GitHub-Hosted And Larger Runners: Specs, Software And Networks — GitHub Actions (GH-200) Exam Prep
- Self-Hosted Runners At Scale: Labels, Groups And ARC — GitHub Actions (GH-200) Exam Prep
- Usage, Billing And The Audit Log — GitHub Actions (GH-200) Exam Prep
- GITHUB_TOKEN: Least Privilege, Job By Job — GitHub Actions (GH-200) Exam Prep
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep
- Faster And Cheaper: Where The Minutes Go — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep