github-to-rithub/docs/github-actions-to-rithub-ci.md
caelum0x 4f2842a38b docs: describe Rithub on its own terms across README, docs and CLI
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 00:35:48 +03:00

3.5 KiB

GitHub Actions → Rithub CI

Rithub Actions is deliberately built to be close to GitHub Actions syntax (it executes the same workflow YAML format via act-compatible runners). That means most simple workflows need small, mechanical changes, not a rewrite — but "close to" is not "identical", and you should verify this against your own runner, not take it on faith.

This CLI copies your .github/workflows/*.yml files over as part of the normal code migration (they're just files in the repo), but it does not rewrite them, enable Actions on the target repo, or register a runner for you. Those are separate, deliberate steps below.

Step 1 — confirm Rithub Actions is actually enabled on your target server

Check with your Rithub admin (or, if you're self-hosting, your own app.ini) whether Actions is turned on, and whether a runner is registered and online. Without a registered runner, workflows will queue forever and silently never run — this is the single most common "CI doesn't work after migration" cause, and it has nothing to do with your YAML.

curl -s -H "Authorization: token $RITHUB_TOKEN" \
  https://rithub.dev/api/v1/repos/<owner>/<repo>/actions/tasks

Step 2 — enable Actions on the migrated repo

Repo migration does not automatically flip on Actions for the new repo. In the repo's Settings on Rithub, enable "Actions" under Units/Features (or via the API: PATCH /repos/{owner}/{repo} with "has_actions": true, depending on your Rithub version).

Step 3 — move your workflow files

Your workflows already live at .github/workflows/*.yml after migration — Rithub Actions reads from the exact same path, so most of the time there's nothing to move.

Step 4 — fix the real differences

These are the differences that actually bite in practice, not a hypothetical list:

  • uses: actions/checkout@v4 and other hosted GitHub Marketplace actions. Rithub Actions can run many of these unmodified if your runner has network access to github.com (it fetches the action's repo directly), but this depends on your runner's network policy. If your Rithub instance has outbound network restricted, mirror the specific actions you depend on into your own org and reference them by your own path instead.
  • secrets.GITHUB_TOKEN. Rithub Actions provides its own equivalent token scoped to the Rithub API, not GitHub's. Any step that calls api.github.com directly needs a real Rithub token in a new repo secret instead.
  • GitHub-specific context values (github.event.pull_request.* shapes can differ slightly, some newer GitHub context fields don't exist yet in a given Rithub version). Test the exact trigger you depend on (push, pull_request, release) rather than assuming parity.
  • Marketplace actions that call GitHub-only APIs (e.g., posting a GitHub Checks run, commenting via the GitHub API) will fail or silently no-op on Rithub — they're calling the wrong platform's API by design. Replace with the Rithub-API equivalent or drop the step.
  • Runner labels (runs-on: ubuntu-latest) only work if a runner registered on your Rithub instance actually advertises that label. Check what your runner offers; don't assume GitHub's hosted runner image.

Step 5 — verify, don't assume

Push a trivial commit and watch the Actions tab on the migrated repo run end-to-end at least once before you rely on it. A workflow that "looks right" in the YAML but references an unreachable action or a runner label nobody registered will fail or hang silently.