Deploy
Run GitHub Actions jobs on Skippr-managed runners. GitHub stays the workflow engine; Skippr starts a runner when a matching job is queued. You keep using runs-on labels in your workflow YAML.
The first sub-product is Runner. That guide shows the same GitHub install, repository bind, and pool create as CLI, Terraform, CDKTF TypeScript, or CDKTF Python. Long-running machines are not a product yet.
Status: Production. Connect GitHub from the Runner guide. See the API action reference for the full command list. skippr-cloud deploy runner create-checkout-session returns a Checkout URL. Complete the session with skippr-cloud deploy runner complete-checkout-session after payment. Windows and Linux ARM fail closed until a live RunnerHost exists.
At a glance
| Hostname | deploy.{region}.cloud.skippr.io |
| Auth | Cloud JWT (Authorization: Bearer) or SigV4 service deploy |
| Protocol | Cloud JSON (X-Cloud-Target: CloudDeploy.Runner.<Action>) |
| CLI | skippr-cloud deploy runner <operation> |
What you can do
- Connect the GitHub App, or record an existing installation.
- Bind a repository to that installation.
- Create a runner pool with a size label such as
skippr-linux-x64-2. - List and cancel runner sessions after GitHub queues a matching job.
- Delete a pool: in-flight sessions stop, then the pool is removed.
- Manage pool variables and secret references.
Webhook delivery uses the platform hostname. You do not paste a webhook secret.