coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(ISSUE-WP-0006): Forgejo-only language and projection boundary
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Build and Publish Container Image / build-and-push (push) Successful in 34s
Details

Browse source 
Prefer Forgejo as the self-hosted forge product. Keep Gitea only as the
Gitea-compatible API identifier (module backends/gitea, type string
gitea). FORGEJO_TOKEN is preferred; GITEA_* remains a deprecated alias.

INTENT/SCOPE quote ACT-ADR-005: issue-core is not the fleet ops claim
queue. Connector docs describe repo work record → hub index → optional
Forgejo projection, not activity-core → issue-core → harness.

Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
This commit is contained in:
tegwick 2026-09-14 04:52:58 +02:00
parent f9d276dadf
commit ee9b85215d
34 changed files with 410 additions and 263 deletions
Download patch file Download diff file Expand all files Collapse all files

17
integration/gitea-backend.integration.yaml
View file

@ -1,9 +1,10 @@
schema_version: open-reuse.integration.v0.1
id: issue-core-gitea
name: issue-core Gitea Backend
name: issue-core Forgejo Backend
description: >
Pluggable remote backend that maps the issue-core unified issue model onto the
Gitea issues API for external-tracker projection and synchronization.
Forgejo issues API (Gitea-compatible) for external-tracker projection and
synchronization. Gitea is not a second supported product.
status: registered
owner: issue-core
@ -13,9 +14,9 @@ local:
system: issue-core
upstream:
name: Gitea
project_url: https://github.com/go-gitea/gitea
homepage: https://about.gitea.com/
name: Forgejo (Gitea-compatible API)
project_url: https://codeberg.org/forgejo/forgejo
homepage: https://forgejo.org/
version_policy: gitea-api-v1
monitor:
releases: true
@ -29,14 +30,14 @@ reuse:
- plugin
risk_level: medium
rationale: >
Gitea REST API is wrapped behind the RemoteBackend interface; local task
lifecycle semantics remain stable across backend swaps.
Forgejo (Gitea-compatible) REST API is wrapped behind the RemoteBackend
interface; local task lifecycle semantics remain stable across backend swaps.
boundary:
type: adapter
local_adapter: issue_core.backends.gitea.backend.GiteaBackend
local_interface: issue_core.core.interfaces.RemoteBackend
reused_surface: Gitea /api/v1 issues, labels, milestones, comments
reused_surface: Forgejo (Gitea-compatible) /api/v1 issues, labels, milestones, comments
contracts:
- issue-core.backend.v1
fragility_points: