docs(factory): issue labels and cross-repository dispatch (#31)#32
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Review: APPROVED — ar-31-review-agentrelay-com Reviewed commit No changes requested. Per merge policy this PR is left open for human review and merge — not auto-merged. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughAdded a Factory issue-label and repository-routing documentation page covering routing semantics, execution shapes, limits, checkout behavior, and dispatch commands. Linked it from related Factory docs, added it to navigation, and tested navigation/search indexing. ChangesFactory issue routing
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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. Comment |
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |
|
The example shouldn't have |
workspaceId is optional and Factory resolves the active workspace automatically, so including it as a required-looking field in the config example could mislead readers. Address review feedback from khaliqgant.
|
Addressed — thanks for the catch. Finding: the Fix (commit Validation: |
Closes #31.
What this adds
A new, navigable and searchable Factory docs page — Issue labels and repository routing (
web/content/docs/factory/issue-routing.mdx) — plus cross-links from the Introduction, Configuration, and Safety scope pages, a nav entry, and a nav/search regression test.The page covers, for Factory v0.1.34:
safety.requireLabelopts an issue in and is not a repository route;repos.byLabelselects repositories; execution-shape labels choose how routes become agents.agent:single,agent:team,agent:workflow, with the exact agent fan-out for each.teamwhen no explicit shape label is present.factory.config.jsonexample usingcloneRoot, plus aclonePathsvariant, and the collision-safefactory-reporouting label.triage.maxImplementers(1–6, default 2) and the effective team route capmin(triage.maxImplementers, 4), including the refusal-on-overflow behavior.factory dispatch <number|mounted-path> --dry-run,factory dispatch <number|mounted-path>,factory start --mode live— and the note thatfactory dispatchdoes not accept an issue URL.v0.1.34tag.Reviewer verification (ar-31-review-agentrelay-com)
Independent of the implementer's checks, I verified:
vitest run→ 22 passed (incl. the newweb/lib/test/product-docs.test.ts).tsc --noEmit→ clean.next build --webpack→ exit 0, 386 pages generated;/docs/factory/issue-routingand its/markdownmirror render.factorySectionnav and is picked up bygetProductSearchIndex(headings + body), so it is reachable and searchable.src/triage/heuristic.ts,src/config/schema.ts,src/orchestrator/factory.ts,.agentworkforce/features/manifest.yaml) and confirmed — including case-insensitive label matching, thesingle/team/workflowfan-out, inferred team scope,min(maxImplementers, 4)cap with refusal on overflow, and thedispatchURL limitation. Terminology matches the manifest entriestriage-team-scopeandtriage-shape-labels.v0.1.34git tag exists and all four referenced source files resolve at that tag.Docs correctly pin to v0.1.34 — consistent with the existing
factorySection.versionand sibling factory docs — even though the local factory checkout has since advanced.Merge policy
Opened for human review and approval. Do not auto-merge — a human should review and merge.
🤖 Generated with Claude Code