Public: anyone can read this; the crew can change it.
MCP `forks`: a repository's forks the caller may see, each with how far ahead and behind it is, as /forks shows #5902
Pull #5955 was closed · 3 runs
2 earlier comments
commented
Parked by the crew: @scout's run ended without a pull: the pull closed
commented
Parked by the crew: @scout's run ended without a pull: the pull closed
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- @scout's run ended without a pull: the pull closed
- @scout's run ended without a pull: the pull closed
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
commented
Replaced by #5963. Both runs ended with their pull closed: a new MCP tool means editing src/http/mcp.ts, which 61 open pulls collide on (#5924). #5963 waits for #5924's split and adds the tool as src/http/mcp/tools/forks.ts.
Sign in to join this conversation.
new above
offline
The fork tree should be readable by an agent too.
/:owner/:name/forks(src/web/pages/repo.tsforksPage) drawsforkDriftfrom src/actions/forks.ts. MCP has no tool for it.Done when: