Self-hosted
Ephemeral runner
Quick answer
An ephemeral runner executes exactly one job and is then destroyed, guaranteeing no state carries into the next job.
An ephemeral runner executes exactly one job and is then destroyed, guaranteeing no state carries into the next job.
Why it matters
It is the only safe configuration for public repositories, because a persistent runner lets one job leave something behind for the next one to find.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Actions Runner ControllerActions Runner Controller (ARC) is an open-source Kubernetes operator that provisions and autoscales self-hosted GitHub Actions runners as pods in your own cluster.Autoscaling runnerAn autoscaling runner is a self-hosted runner whose instance count grows and shrinks automatically in response to queued jobs.Runner groupA runner group is a collection of runners with access policies controlling which organisations and repositories may use them.Self-hosted runnerA self-hosted runner is a machine you own and operate that connects to GitHub to execute Actions jobs.