Gitea/Forgejo adapter for v1 operations #6

New issue

deadstyle · 2026-10-01T21:55:16-05:00

deadstyle commented

2026-10-01 21:55:16 -05:00

Problem

v1 targets Forgejo/Gitea. The core and UI need a real adapter that implements the Forge interface against git.bobparsons.dev for every v1 operation.

Plan

Implement internal/forge/gitea, using the client chosen in the SDK spike:

list repos for the current user, sorted by last activity (compute it if the API's "updated" isn't accurate enough; see docs/architecture.md)
list, get, merge, close change requests, including CI state from commit statuses
approve (the forge.Approver capability)
list issues (excluding PRs), edit an issue body (for Renovate dashboard ticks), comment, close
list releases
Actions capabilities, limited to what the Actions spike found available
pagination, ErrNotFound/ErrUnauthorized/ErrRateLimited mapping, Forgejo/Gitea version detection

Tests: run the forgetest contract suite against httptest servers that serve recorded responses from testdata/.

Plan-review additions (#17)

Report capability availability per the shape #4 settles: adapter support, plus server-version gates (detected once at connect) and repo permissions (from the repo's permissions field), each with a disabled reason.
Merge sends head_commit_id from MergeOpts; a mismatch maps to a distinct, typed error so the UI can say "this PR changed since you confirmed".
Comment and Close route on the typed resource reference from #4.

Depends on

The SDK spike, the domain model / Forge interface ticket, and the Actions spike (for the Actions capabilities only).

Context

docs/architecture.md → API mapping (Gitea / Forgejo column).
ADR 0002, and go-development → Layering (no SDK type leaves the adapter) and Errors.

Out of scope

The GitHub and GitLab adapters.

## Problem v1 targets Forgejo/Gitea. The core and UI need a real adapter that implements the `Forge` interface against git.bobparsons.dev for every v1 operation. ## Plan Implement `internal/forge/gitea`, using the client chosen in the SDK spike: - list repos for the current user, sorted by last activity (compute it if the API's "updated" isn't accurate enough; see `docs/architecture.md`) - list, get, merge, close change requests, including CI state from commit statuses - approve (the `forge.Approver` capability) - list issues (excluding PRs), edit an issue body (for Renovate dashboard ticks), comment, close - list releases - Actions capabilities, limited to what the Actions spike found available - pagination, `ErrNotFound`/`ErrUnauthorized`/`ErrRateLimited` mapping, Forgejo/Gitea version detection Tests: run the `forgetest` contract suite against `httptest` servers that serve recorded responses from `testdata/`. ### Plan-review additions (#17) - Report capability availability per the shape #4 settles: adapter support, plus server-version gates (detected once at connect) and repo permissions (from the repo's `permissions` field), each with a disabled reason. - Merge sends `head_commit_id` from `MergeOpts`; a mismatch maps to a distinct, typed error so the UI can say "this PR changed since you confirmed". - Comment and Close route on the typed resource reference from #4. ## Depends on The SDK spike, the domain model / `Forge` interface ticket, and the Actions spike (for the Actions capabilities only). ## Context - `docs/architecture.md` → API mapping (Gitea / Forgejo column). - ADR 0002, and `go-development` → Layering (no SDK type leaves the adapter) and Errors. ## Out of scope The GitHub and GitLab adapters.

deadstyle added the

feature

opus

labels

2026-10-01 21:55:25 -05:00

~~deadstyle referenced this issue 2026-10-01 22:08:47 -05:00~~

Config: TOML config and state, token resolution, host selection #5

deadstyle referenced this issue

2026-10-01 22:22:37 -05:00

Fold plan-review findings into tickets and docs #17

deadstyle referenced this issue

2026-10-02 10:29:48 -05:00

Fold plan-review findings into tickets and docs #17

deadstyle referenced this issue

2026-10-02 10:34:43 -05:00

Spike: Forgejo Actions API coverage on our instance #1

deadstyle referenced this issue

2026-10-02 11:46:15 -05:00

docs: plan review, fold-in of its findings, and v1 product decisions #18

deadstyle referenced this issue from a pull request that will close it,

2026-10-02 12:30:36 -05:00

feat(gitea): Gitea/Forgejo adapter for v1 operations #27

deadstyle referenced this issue from a commit

2026-10-02 12:30:37 -05:00

test(gitea): contract and adapter tests with recorded fixtures

deadstyle referenced this issue from a commit

2026-10-02 12:30:37 -05:00

test(gitea): unpaginated jobs route, fix JobLog nil close, contextcheck

deadstyle referenced this issue from a commit

2026-10-02 12:30:37 -05:00

test(gitea): cover push access, labels, closed issue state, repo order

deadstyle closed this issue

2026-10-02 12:32:02 -05:00

deadstyle commented

2026-10-02 12:32:02 -05:00

🤖 Merged in #27. lazyforge can now sign in to a Forgejo or Gitea host, list repos with your access level, read and merge PRs (a merge refuses if the PR changed since you looked), read and edit issues, comment, close, list releases, and on Forgejo list Actions runs, jobs and logs.

Sign in to join this conversation.