Wiki / Preview v0.1.10
Workflows on your hardware.
Rookrunner is a self-hosted runner for a growing subset of GitHub Actions-style workflows. You operate the worker and the machine that runs jobs.
Preview status
v0.1.10 is an early preview. Workflow support and interfaces are still changing. Rookrunner is not a drop-in replacement for GitHub-hosted Actions and does not claim full Actions compatibility.
How a run moves
GitHub workflow
A workflow event is selected by the poller, which checks the repository's trust rules before creating a run.
Local worker
The worker accepts jobs through a private local socket and runs them one at a time in Docker containers.
Run record
Use the command line to follow state and logs, inspect artifacts, and post an optional commit status.
How it differs from hosted Actions
| Hosted Actions | Rookrunner v0.1.10 |
|---|---|
| GitHub provides the hosted runner. | You operate the Linux host, Docker engine, worker, and runner image. |
| GitHub Actions supports a broad workflow and action ecosystem. | Rookrunner implements a documented subset; unsupported features are refused rather than promised as equivalent. |
| Runner environments follow GitHub's hosted images. | Jobs use an operator-provided, digest-pinned container image. |
| GitHub defines its own trust and secret behavior. | Rookrunner applies local trust checks. Forks are refused by default, and optional secrets are gated by explicit worker settings. |