CI
Run pull request and push checks on run.cloud sandboxes instead of GitHub-hosted runners. Results show up as normal GitHub Check Runs (run.cloud / <job>), so you can require them in branch protection.
Jobs boot from any OCI image, run shell steps against the commit SHA, and tear
down when they finish. You keep your workflows under .github/workflows/
and opt in a job with runs-on: runcloud.
Why use it
- No Actions minutes for opted-in jobs — compute is billed as sandbox usage on your run.cloud org.
- Same PR UI — green / red checks on the commit, re-run from the Checks tab.
- Familiar shape — stay in
.github/workflows/with a small, documented subset of GitHub Actions syntax. - Secrets you already manage — inject secret groups from your run.cloud org (not the GitHub Actions secrets store).
Quick path
1
Connect GitHub
In the dashboard, open GitHub CI
and install the Run Cloud CI GitHub
App on the repositories you want. That links the installation to your
run.cloud org so only bound orgs ever run jobs.
2
Add a workflow
Create
.github/workflows/ci.yml with at least one job that sets
runs-on: runcloud. See GitHub workflows for full
examples.3
Open a pull request
Checks named
run.cloud / <job> appear on the head commit. Require
them under branch protection when you are ready.Minimal example
What runs where
You can mix both in the same repository: keep heavy or unsupported Actions jobs
on GitHub, and move simple shell CI to run.cloud.
Next
- GitHub workflows — multi-job examples, path filters, monorepos, branch protection.
- Secrets in CI — inject org secret groups and
${{ secrets.NAME }}. - Configuration reference — supported fields, defaults, and the documented subset of GitHub Actions syntax.