docs(codeberg): clarify Codeberg support positioning — Forgejo-native vs Gitea-compatible vs Codeberg-hosted vs mirror-releases #358

New issue

Closed

opened 2026-07-03 23:42:49 +02:00 by bosun · 1 comment

bosun commented

2026-07-03 23:42:49 +02:00

Owner

Empirical finding (external cold-read round 2)

External reviewer named 4 distinct positioning claims that are all different:

Forgejo-native — primary Forgejo instance (private, self-hosted)
Gitea-compatible — works with Gitea too (Forgejo forked from Gitea)
Codeberg-hosted — primary Codeberg instance (public Forgejo)
Mirror-releases-to-Codeberg — private dev on Forgejo, public releases mirrored to Codeberg (our current adoption pattern)

Our documentation conflates them. External adopter can't tell what our claim actually is.

Blocking rationale

Adopters need to know if this tool fits their configuration. If they run on Gitea, does it work? If they use Codeberg as primary dev, does it work? If they mirror to Codeberg, is release-page mirroring supported?

Fix path

Add a Positioning section to README naming the 4 axes explicitly
For each axis: state SUPPORTED (with evidence) vs UNTESTED vs NOT-SUPPORTED
Named tested Forgejo version + Codeberg version if applicable
Link to Codeberg mirror-workflow docs (release-toolkit#309 provides the wiring)

Verification AC

Adopter can read Positioning section and know which of the 4 axes their setup falls under
External cold-read round 3 finds no Codeberg positioning ambiguity

Anchor

External outside-model cold-read round 2 (fresh ChatGPT session, 2026-07-03 late) returned new findings after Pilot Cold-Read delta had cleared. External verdict: 'promising but not yet trustworthy.' Operator ratified delta plan 2026-07-03 23:35. This tracker addresses one of the round-2 findings. Success criterion: subsequent external cold-read returns no further objections of this class.

## Empirical finding (external cold-read round 2) External reviewer named 4 distinct positioning claims that are all different: 1. **Forgejo-native** — primary Forgejo instance (private, self-hosted) 2. **Gitea-compatible** — works with Gitea too (Forgejo forked from Gitea) 3. **Codeberg-hosted** — primary Codeberg instance (public Forgejo) 4. **Mirror-releases-to-Codeberg** — private dev on Forgejo, public releases mirrored to Codeberg (our current adoption pattern) Our documentation conflates them. External adopter can't tell what our claim actually is. ## Blocking rationale Adopters need to know if this tool fits their configuration. If they run on Gitea, does it work? If they use Codeberg as primary dev, does it work? If they mirror to Codeberg, is release-page mirroring supported? ## Fix path - Add a Positioning section to README naming the 4 axes explicitly - For each axis: state SUPPORTED (with evidence) vs UNTESTED vs NOT-SUPPORTED - Named tested Forgejo version + Codeberg version if applicable - Link to Codeberg mirror-workflow docs (release-toolkit#309 provides the wiring) ## Verification AC - Adopter can read Positioning section and know which of the 4 axes their setup falls under - External cold-read round 3 finds no Codeberg positioning ambiguity ## Anchor External outside-model cold-read round 2 (fresh ChatGPT session, 2026-07-03 late) returned new findings after Pilot Cold-Read delta had cleared. External verdict: 'promising but not yet trustworthy.' Operator ratified delta plan 2026-07-03 23:35. This tracker addresses one of the round-2 findings. Success criterion: subsequent external cold-read returns no further objections of this class.

bosun added the

priority/high

size/S

kind/docs

labels

2026-07-03 23:42:49 +02:00

quartermaster referenced this issue from a commit

2026-07-04 00:03:00 +02:00

docs(codeberg): 4-axis positioning table (Forgejo/Gitea/Codeberg) (#358)

quartermaster referenced this issue

2026-07-04 00:03:29 +02:00

docs: round-2 adopter-honesty bundle — tokens + Codeberg positioning + tag creation (#356 #358 #359) #364

quartermaster referenced this issue from a commit

2026-07-04 00:10:32 +02:00

docs(codeberg): 4-axis positioning table (Forgejo/Gitea/Codeberg) (#358)

release-bot referenced this issue

2026-07-04 00:10:59 +02:00

chore(release): v0.26.0 #327

quartermaster commented

2026-07-04 00:15:13 +02:00

Owner

Delta merged via PR #364 at 886abbb. Positioning table added to README.md naming all 4 Forgejo-ecosystem axes explicitly (Forgejo-native ✅, Gitea-compatible ⚠️ UNTESTED, Codeberg-hosted ⚠️ UNTESTED, mirror-releases-to-Codeberg ✅) with evidence per row. integration.md cross-references the README table.

Delta merged via [PR #364](https://git.frankenbit.de/frankenbit/release-toolkit/pulls/364) at 886abbb. Positioning table added to `README.md` naming all 4 Forgejo-ecosystem axes explicitly (Forgejo-native ✅, Gitea-compatible ⚠️ UNTESTED, Codeberg-hosted ⚠️ UNTESTED, mirror-releases-to-Codeberg ✅) with evidence per row. integration.md cross-references the README table.

quartermaster closed this issue

2026-07-04 00:15:13 +02:00