Migrate from GitHub Actions
Copy your workflows, update runner labels, and compare results before switching required checks.
Avrea CI runs your workflows directly on Avrea. Keep the GitHub Actions YAML
syntax you already use, place your workflows in .avrea/workflows/, and let
Avrea schedule jobs, run them in isolated VMs, and collect their results.
Your repository stays on GitHub. Pushes, pull requests, and manual runs can start Avrea CI workflows. Follow runs and inspect job logs in the Avrea console, with checks reported back to GitHub.
| Avrea CI | GitHub Actions on Avrea runners | |
|---|---|---|
| Workflow location | .avrea/workflows/ | .github/workflows/ |
| Workflow scheduling | Avrea | GitHub Actions |
| Job execution | Avrea VMs | Avrea VMs |
| Secrets and variables | Configure in Avrea | Configure in GitHub |
| Getting started | Copy workflows and review compatibility | Change runs-on to an Avrea label |
Both can run in the same repository. Avrea CI supports a subset of GitHub Actions features; check the compatibility guide before moving workflows that deploy, publish, or depend on GitHub services.
Connect your repository through the Avrea GitHub App and contact support@avrea.com to have Avrea CI and repository mirroring enabled for the repository.
Commit this file, then push to trigger the run:
name: Hello Avrea CI
on: push
jobs: hello: runs-on: avrea-ubuntu-24.04 steps: - uses: actions/checkout@v7 - run: git rev-parse HEAD - run: echo "Hello from Avrea CI"Open the repository in the Avrea console and select the run labeled Avrea CI. Each job gets its own VM; use job outputs for small values and artifacts for files that another job needs.
Migrate from GitHub Actions
Copy your workflows, update runner labels, and compare results before switching required checks.
Run workflows
Secrets and variables
Configure credentials and scoped values for push and manual workflows.
Compatibility and limits