RISC-V GitHub Runners
Run your GitHub Actions CI on real RISC-V hardware. Install the app once, and runners are provisioned automatically whenever your jobs need them.
Install the GitHub App
One installation covers your repository. No tokens to generate, nothing to renew, no waiting on this page.
Install on GitHubTakes about two minutes. Read the setup guide
How it works
Install the app on your repository
Choose the repositories that should have access to RISC-V runners. You can change this any time from your GitHub settings.
Point your workflow at a board
Add a board label to runs-on in your workflow file:
jobs:
build:
runs-on: [self-hosted, visionfive2]
steps:
- uses: actions/checkout@v4
- run: make test
Push your code
When the job is queued, a runner is provisioned on a board for your repository, usually within a few minutes. Every job runs on a fresh runner: when a job finishes, its runner retires itself and a replacement is prepared automatically, so nothing carries over between jobs.
Available boards
VisionFive 2
Accepted labels
visionfive2 vf2 vision-five-2
Milk-V Pioneer
Accepted labels
milkv-pioneer pioneer milk-v-pioneer
Banana Pi BPI-F3
Accepted labels
banana-pi-f3 bpi-f3 banana-pi
Runner environment
Runner software
RISC-V port of the GitHub Actions runner
Runner lifetime
One job, then a fresh runner takes its place
Need help?
Write to us at cloud-v@10xengineers.ai
Include your repository name, the board label you used, and any error you saw, so we can help you faster.