docs(direction): commit forge-agnostic support as a maintained direction#1575
Merged
Conversation
GitHub stays the primary forge; Gitea and GitLab are community-supported targets via the existing community adapters at packages/adapters/src/community/forge/. Long-term home for outbound forge operations (PR/issue/review CRUD) is the same per-forge adapter that already handles inbound webhooks today. Closes the open direction question that has been blocking PR #1104 (forge-agnostic workflow commands) for ~8 days. The architectural cleanup — migrating PR #1104's interim forge-cli.ts into the existing community adapters — is tracked separately as #1574 and is not a precondition for merging #1104.
📝 WalkthroughWalkthroughThis PR adds a single clarifying bullet point to the maintainer direction document specifying that Archon is forge-agnostic, with GitHub as the primary forge and Gitea/GitLab supported via community adapters, with a shared per-forge adapter handling both inbound webhooks and outbound PR/issue/review operations. ChangesDocumentation Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.archon/maintainer-standup/direction.md (1)
18-18: ⚡ Quick winTighten this clause for scanability and fix hyphenation.
Line 18 is directionally correct, but it’s doing a lot in one bullet; consider tightening it to match the quick-scan intent of this doc, and change “community supported” to “community-supported.”
✍️ Suggested rewrite
-- **Forge-agnostic.** GitHub is the primary forge, but Gitea and GitLab are community supported targets via community adapters at `packages/adapters/src/community/forge/`. Long-term home for outbound forge operations (PR/issue/review CRUD) is the same per-forge adapter that handles inbound webhooks. New forges land as new community adapters that implement the shared interface. +- **Forge-agnostic.** GitHub is the primary forge. Gitea and GitLab are community-supported targets via adapters in `packages/adapters/src/community/forge/`. Outbound forge operations (PR/issue/review CRUD) live in the same per-forge adapter that handles inbound webhooks; new forges should land as community adapters implementing the shared interface.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.archon/maintainer-standup/direction.md at line 18, Tighten and hyphenate the "Forge-agnostic." bullet: rewrite the single long sentence into a concise, scan-friendly phrase that uses "community-supported" (hyphenated) and keeps the essential points — GitHub primary, Gitea/GitLab supported via community adapters, and the long-term home for outbound forge operations is the same per-forge adapter that handles inbound webhooks — while retaining the reference to packages/adapters/src/community/forge/ so readers can find the adapters path.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.archon/maintainer-standup/direction.md:
- Line 18: Tighten and hyphenate the "Forge-agnostic." bullet: rewrite the
single long sentence into a concise, scan-friendly phrase that uses
"community-supported" (hyphenated) and keeps the essential points — GitHub
primary, Gitea/GitLab supported via community adapters, and the long-term home
for outbound forge operations is the same per-forge adapter that handles inbound
webhooks — while retaining the reference to
packages/adapters/src/community/forge/ so readers can find the adapters path.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 31aa3d5c-5ba3-4460-98c7-8903ce3a682a
📒 Files selected for processing (1)
.archon/maintainer-standup/direction.md
Closed
cropse
pushed a commit
to cropse/Archon
that referenced
this pull request
May 19, 2026
…ion (coleam00#1575) GitHub stays the primary forge; Gitea and GitLab are community-supported targets via the existing community adapters at packages/adapters/src/community/forge/. Long-term home for outbound forge operations (PR/issue/review CRUD) is the same per-forge adapter that already handles inbound webhooks today. Closes the open direction question that has been blocking PR coleam00#1104 (forge-agnostic workflow commands) for ~8 days. The architectural cleanup — migrating PR coleam00#1104's interim forge-cli.ts into the existing community adapters — is tracked separately as coleam00#1574 and is not a precondition for merging coleam00#1104.
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.
Summary
direction.md: GitHub is primary; Gitea and GitLab are community-supported targets via the existing community adapters atpackages/adapters/src/community/forge/.forge-cli.tsinto the existing community adapters — is tracked as Refactor: migrate forge-cli.ts logic into community/forge adapters (follow-up to #1104) #1574 and is not a precondition for merging feat: forge-agnostic workflow commands (Gitea/GitLab support) #1104.Why now
@truck0321's PR #1104 has been waiting on a maintainer direction call. The implementation is well-tested and clean; the only outstanding question was whether forge support beyond GitHub is in scope. The answer is yes — but as community-tier (matching how Pi is positioned vs. Claude/Codex), not first-class core support.
Filing this as a separate one-line PR so the direction call is its own auditable change, decoupled from any code that follows it.
Test plan
Summary by CodeRabbit