GloriousFlywheel Forge Support Matrix 2026-04-16
Snapshot date: 2026-04-16
Purpose
Make the forge boundary concrete enough that docs, backlog, and product claims stop drifting.
GitHub owner: #211
Support Matrix
| Dimension | GitHub | GitLab | Codeberg |
|---|---|---|---|
| Product posture | primary | compatibility | downstream compatibility with caveats |
| Runner substrate fit | strongest current fit via ARC scale sets and org-native Actions flows | legacy and migration support via self-managed runners and Kubernetes executor | downstream fit only; shared CI is constrained and heavier use expects self-hosted agents |
| Identity and app model | strongest current fit | compatibility login and legacy control surfaces still exist | no primary identity/control investment should be implied |
| Dashboard/operator story | current strategic direction | compatibility mutation and legacy control backing still present | not a primary dashboard/control driver |
| Cache and builder story | primary product narrative | compatibility only | downstream-only narrative |
| Docs stance | lead with this | clearly marked compatibility/migration path | clearly marked caveated downstream path |
| Backlog stance | active product shaping | harden only where still needed | defer until GitHub-first surface is coherent |
Execution Consequence
The repo should treat forge work in this order:
- GitHub-first product docs and migration surfaces
- GitLab compatibility hardening for real remaining consumers
- Codeberg compatibility docs and examples only after the GitHub-first path is coherent
Claim Boundary
What the repo can honestly claim today:
- GitHub is the primary product surface
- GitLab remains supported as an interoperability and migration lane
- Codeberg matters for FOSS credibility, but not as the primary control plane
What the repo should not claim today:
- equal maturity across GitHub, GitLab, and Codeberg
- a forge-neutral control plane with identical operator experience
- a production-ready Codeberg-first story
Primary Docs That Should Reflect This
README.mddocs/runners/github-actions.mddocs/guides/github-app-adoption.mddocs/guides/cross-forge-ci.mddocs/runners/self-service-enrollment.mddocs/runners/runner-selection.md
Acceptance Criteria
- primary docs lead with GitHub usage
- GitLab-specific docs are framed as compatibility or migration
- Codeberg-specific docs are framed as downstream support with caveats
- no primary surface implies equal maturity across the three forge families