docs: plan Forgejo provider implementation#265
Merged
mariusvniekerk merged 9 commits intomainfrom May 7, 2026
Merged
Conversation
Collaborator
Author
|
This change is part of the following stack:
Change managed by git-spice. |
roborev: Combined Review (
|
This was referenced May 7, 2026
Researches Forgejo API compatibility, token scopes, Go SDK options, and local fixture needs for adding Forgejo as the third Middleman provider after GitHub and GitLab.
Expands the Forgejo provider plan to add Gitea as a sibling provider, pin separate SDKs for each, and call out Forgejo-specific Actions behavior instead of treating both APIs as identical.
Reworks the provider plan so Forgejo and Gitea use a shared gitea-like implementation for common provider behavior, keeping the concrete provider packages focused on SDK adaptation and true API divergence such as Forgejo Actions.
Adds a GitHub capability parity target for Forgejo and Gitea, including read features, mutations, workflow approval, ready-for-review gaps, and tests that keep capability flags honest.
Clarifies the read-only MVP boundary, moves GitHub-parity mutations to post-MVP work, fixes SDK base URL guidance, adds required UI e2e coverage, and documents config regression and insufficient-scope error tests.
Records that the remaining roborev jobs for earlier Forgejo and Gitea provider-plan commits were resolved by the existing follow-up spec fixes and closed.
Clarifies that Forgejo and Gitea token resolution is keyed by provider and host, with public-host defaults plus explicit platform token envs for federated and self-hosted instances.
Records the kata epic and implementation task graph for the Forgejo and Gitea provider work, including MVP sequencing and post-MVP parity tasks.
mariusvniekerk
force-pushed
the
forgejo-provider-impl
branch
from
ba45b96 to
d62e56b
Compare
roborev: Combined Review (
|
The Playwright image pull happens before CI job steps can run, so our retry wrapper cannot help when MCR blocks or flakes. Revert the e2e jobs to install the requested browser on the hosted runner instead of running inside the Playwright container.
roborev: Combined Review (
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs: plan Forgejo provider implementation
Researches Forgejo API compatibility, token scopes, Go SDK options, and local fixture needs for adding Forgejo as the third Middleman provider after GitHub and GitLab.
docs: include Gitea in provider plan
Expands the Forgejo provider plan to add Gitea as a sibling provider, pin separate SDKs for each, and call out Forgejo-specific Actions behavior instead of treating both APIs as identical.
docs: share Forgejo and Gitea provider core
Reworks the provider plan so Forgejo and Gitea use a shared gitea-like implementation for common provider behavior, keeping the concrete provider packages focused on SDK adaptation and true API divergence such as Forgejo Actions.
docs: align Forgejo plan with GitHub provider features
Adds a GitHub capability parity target for Forgejo and Gitea, including read features, mutations, workflow approval, ready-for-review gaps, and tests that keep capability flags honest.
docs: resolve Forgejo provider design review
Clarifies the read-only MVP boundary, moves GitHub-parity mutations to post-MVP work, fixes SDK base URL guidance, adds required UI e2e coverage, and documents config regression and insufficient-scope error tests.
chore: close remaining Forgejo provider reviews
Records that the remaining roborev jobs for earlier Forgejo and Gitea provider-plan commits were resolved by the existing follow-up spec fixes and closed.
docs: require host-scoped forge tokens
Clarifies that Forgejo and Gitea token resolution is keyed by provider and host, with public-host defaults plus explicit platform token envs for federated and self-hosted instances.
docs: add Forgejo provider kata graph
Records the kata epic and implementation task graph for the Forgejo and Gitea provider work, including MVP sequencing and post-MVP parity tasks.