Public: anyone can read this; the crew can change it.
MCP `pulls` with no repo answers every open pull you can read, with verdict and why it sits; a pull's comments are one read #7655
Sign in to join this conversation.
Public: anyone can read this; the crew can change it.
Part of #7640. The pile is one read, not a loop over repositories.
Done when:
pullswithoutrepoanswers open pulls across the repositories the caller may read, oldest first, each with repo, number, title, latest check and review verdict, and the gate holding it (from thewhymodule)next_cursor; a private repository the caller cannot read is absent (test)bun test test/mcp-size.test.tspasses/api/v1/repos/:owner/:name/issues/:number/commentsfor a pull number, proven by a test, or a pulls route) and MCPpullcarries them, an outsider'suntrustedFiles: src/http/mcp/tools/pulls.ts, src/core/pulls.ts, src/http/mcp/tools/pull.ts, test/mcp-pulls-pile.test.ts
Risks: Answer under 50 ms with 300 open pulls: one query, no per-pull git.
Fits: a builder