Features
The pages below cover what Codebahn adds on top of Forgejo. Stock features (repositories, the API, admin, Actions syntax) are documented upstream.
CI runners
Section titled “CI runners”Every plan includes hosted CI runners in the EU. Most GitHub Actions workflows run unchanged, and you can register your own runner if you need different hardware. See CI runners for compatibility, the pre-cached toolchain, and bring-your-own setup. To get a pipeline running, follow Set up CI.
Billing
Section titled “Billing”Capacity-based plans with no per-seat pricing: you pick a tier by storage and CI minutes, not headcount. CI minutes are hard-capped. When they run out, new jobs are denied with a “CI is paused” message rather than queued, and you can buy top-ups to keep building. See Billing for the full model and Limits for the exact caps.
Workflow directories
Section titled “Workflow directories”Codebahn scans .codebahn/workflows/, .forgejo/workflows/, .gitea/workflows/, and .github/workflows/, then merges the results instead of reading only the first directory found. See Workflow directories for precedence and de-duplication.
Webhooks
Section titled “Webhooks”Post repository events (push, pull request, issues, releases) to your own endpoint, signed so you can verify them. See Webhooks for the Codebahn settings path and signature verification.
What Codebahn adds to Forgejo
Section titled “What Codebahn adds to Forgejo”A summary of what the managed layer abstracts, adds, and changes compared to stock Forgejo. See What Codebahn adds to Forgejo.