Repository navigation
docs(vendor-neutrality): cite the open forge/runtime extension-point issues - #614
Merged
Merged
Conversation
…issues The vendor-neutrality doc named the forge backends (GitLab, Gitea, Forgejo, Pagure, Bitbucket) and the agentic runtimes but, unlike the VCS section, did not link their tracking issues — so those "extension points" read as hypothetical when they are in fact open, labelled `good first issue`. Wire the existing issues into the doc so every axis has the same labelled-extension-point rigor as VCS: - Agentic runtime axis + status table: link the runtime adapters #313–#322 (Codex, Gemini, local-LLM, Cursor, Aider, Copilot, Goose, Amazon Q, Junie, OpenHands). - Forge/tracker axis + status table: link GitLab #305, Forgejo/Gitea/Codeberg #310, Pagure #312, Bitbucket #306, SourceHut #607, Bugzilla #302; point at the documented "When to replace this tool" recipe in tools/github/tool.md; and state the tracker/source-control separability explicitly. No new issues created — the extension points already existed; this only makes them discoverable from the explainer. Generated-by: Claude Code (Opus 4.8)
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
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.
What
Follow-up to #613. Wires the existing open tracking issues into
docs/vendor-neutrality.mdso the forge/tracker and agentic-runtime axescarry the same labelled-extension-point rigor the VCS section already has.
Why
The merged doc named the forge backends (GitLab, Gitea, Forgejo, Pagure,
Bitbucket) and the agentic runtimes but did not link their tracking
issues, so those "extension points" read as hypothetical — when they are in
fact open, labelled
good first issue. This closes that gap without creatingany new issues.
Changes
feat(adapter/codex): first-class Codex CLI skill runtime #313–feat(adapter/openhands): OpenHands (ex-OpenDevin) autonomous-agent skill runtime #322 (Codex, Gemini, local-LLM, Cursor, Aider, Copilot, Goose,
Amazon Q, Junie, OpenHands).
Forgejo/Gitea/Codeberg feat(tools/forgejo): forge + tracker bridge for Codeberg / Gitea / Forgejo #310, Pagure feat(tools/pagure): tracker bridge for Fedora and pagure.io-hosted projects #312, Bitbucket feat(tools/mail-source/mailman3): add Mailman 3 / Hyperkitty archive backend #306, SourceHut feat(tools/sourcehut): SourceHut (sr.ht) forge bridge — Git + Hg, email-patch review #607,
Bugzilla feat(tools/bugzilla): add tracker bridge for Bugzilla-based projects #302; point at the documented When to replace this tool recipe in
tools/github/tool.md; state tracker/source-control separability explicitly.Notes
them discoverable from the explainer.
🤖 Generated with Claude Code