Git Hosting With Built-In CI Runners

Rithub bundles CI into the same instance as git hosting — register one runner against your Rithub server and every repository on it can run .gitea/workflows/*.yml jobs immediately, with no separate CI product, account, or per-minute bill.

Why "built-in" matters

How the built-in runner actually works

  1. Generate a registration token from the instance's Actions admin settings (instance-wide or per-repository).
  2. Run the act_runner binary on any machine, pointed at the Rithub instance URL with that token:
    act_runner register --instance https://git.ereboslab.com --token <token>
    act_runner daemon
  3. The runner reports online with its labels — on the live Rithub instance this was confirmed as [ubuntu-latest ubuntu-22.04 ubuntu-24.04].
  4. Any repository with Actions enabled can now use it — push a .gitea/workflows/ci.yml with a matching runs-on: label and the job queues automatically.

How it was verified, not just enabled

A registered runner was confirmed online, a real repository was pushed with a workflow file, and the run's status was polled through the API: queued → running → success in under a minute, on infrastructure this instance controls end to end.

Frequently asked questions

What does "built-in" actually mean here?
The CI engine ships with the git-hosting instance — register a runner against the same server, no separate CI product to set up.

How do I register a runner?
Generate a token from Actions admin settings, then run act_runner register + act_runner daemon against the instance URL.

Is the workflow format compatible with GitHub Actions?
Yes, in most cases — rename .github/workflows to .gitea/workflows and existing syntax usually runs unchanged.

Has this actually been run, not just configured?
Yes — a real workflow went queued → running → success on a registered runner, confirmed via the API.

See repositories already running on Rithub

Want an account? Email [email protected] to request access.