Forgejo / Planned

Forgejo CI, on the roadmap.

Interested in Runzivo compute for your Forgejo projects? Help define the instance and workflow requirements for this planned integration.

Planned

Availability

Planned. No Runzivo Forgejo integration is available today. Supported instances, versions and execution capabilities have not been announced.

Want us to prioritize this integration? Tell us what you need and vote on the public roadmap.

Customer demand helps set priorities. A request or vote does not commit a delivery date.

Planned

Codeberg is powered by Forgejo. That does not confirm Runzivo compatibility with Codeberg or another Forgejo instance. Instance policies, authorization and runner access remain unverified. Include Codeberg requirements in your Forgejo roadmap request.

Want us to prioritize this integration? Tell us what you need and vote on the public roadmap.

What this integration supports

Self-hosted Forgejo Actions

The planned integration targets Forgejo Actions on self-hosted instances. Tell us your version and hosting requirements; no instance compatibility is confirmed yet.

Workflow compatibility to verify

Existing GitHub workflow examples do not prove compatibility with Forgejo. A Runzivo recipe will require its own integration tests.

Authorization to establish

Connection permissions, runner registration and removal need a documented, verified path before onboarding is offered.

Forgejo

How connection works

There is no Forgejo connection action in Runzivo today. Share instance requirements through the roadmap without posting private endpoints, tokens or credentials.

Follow the roadmap →

Runner sizes

Forgejo runner sizes and routing labels are unannounced. Do not use GitHub's Runzivo labels as a claim of Forgejo support.

Usage and pricing

Forgejo pricing is unannounced. Current pricing for available Runzivo products does not confirm Forgejo availability or rates.

See full pricing and billing rules →

Pipeline example

A Forgejo recipe awaits verified authorization, runner registration and job execution. Similar workflow syntax alone is not an integration contract.

A Runzivo pipeline recipe will be published after this integration is released and verified in production. No supported Runzivo YAML or runner label is available for this provider today.

Short walkthrough

No verified Runzivo Forgejo demo exists yet. A provider-specific walkthrough will follow implementation and verification.

A provider-specific demonstration will follow a verified release. Explore the existing GitHub walkthrough for available workflows.

Examples you can explore today

GitHub examples target available personal and organization repositories. GitLab.com is not available in production. Follow its roadmap for updates.

Setup and troubleshooting

No Forgejo connection

This is expected for a planned integration. Runzivo has no supported Forgejo runner setup to diagnose today.

Workflow looks compatible

A familiar YAML format does not verify authorization, runner behaviour or job execution. Wait for a Forgejo-specific recipe.

Follow the roadmap →

Your next step

Follow the roadmap and contribute Forgejo requirements. Plan migration only after a verified integration is announced.

Follow the roadmap

Ask Docs

Ask a question and open it in your AI assistant. The prompt tells it to answer from the Runzivo docs and link the pages it used.

Try asking

Your question opens in the assistant you pick, under its own terms. Runzivo does not see or store it.