list_pull_requests / search_pull_requests: expose review decision + combined CI status as optional fields
維護者通常 1 天內回覆
評估
研究方向
從 list_pull_requests 和 search_pull_requests 入口開始，然後將它們的欄位允許清單與 pull_request_read 作業 get_reviews 和 get_status 進行比較。當兩個列出工具都能選擇性地回傳 review_decision 和 status_check_rollup，因而無需針對每個 PR 進行後續呼叫即可提供所要求的 PR 摘要時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
Describe the feature or problem you’d like to solve
list_pull_requests and search_pull_requests return rich per-PR metadata (state, draft, mergeable_state, timestamps, etc.) but neither exposes the PR's review decision (approved / changes requested / review required) or its combined CI/check status. Getting either today requires a separate pull_request_read call per PR (method: get_reviews and/or get_status), which doesn't scale: summarizing N open PRs costs one bulk listing call plus up to 2×N follow-up calls.
Proposed solution
Add optional fields to list_pull_requests's (and search_pull_requests's) fields allow-list:
review_decision: the PR's overall review decision (APPROVED,CHANGES_REQUESTED,REVIEW_REQUIRED, ornull) — equivalent to GitHub's GraphQLreviewDecisionfield, already used bygh pr list --json reviewDecision.status_check_rollup(or similar): the combined CI/check status for the PR's head commit — equivalent to GitHub's GraphQLstatusCheckRollupfield, already used bygh pr list --json statusCheckRollup.
With these available, a single list_pull_requests call per repository would be enough to classify PRs into buckets like "needs review", "blocked/CI failing", "approved and green", etc. — removing the need for any per-PR follow-up call in the common case.
Example prompts or workflows (for tools/toolsets only)
- "Give me a one-table summary of every open PR across these repos: link, title, review status, CI status" — currently requires 1 + 2N calls; with these fields, a single
list_pull_requestscall per repo would suffice. - Daily/weekly PR digest bots that bucket PRs into categories (needs review / blocked / ready to merge / stale) across many repositories.
- Dashboards needing an at-a-glance "is this PR green and approved?" signal for a large PR backlog without pulling full review/check-run detail for each one.
Additional context
This mirrors what GitHub's own CLI (gh pr list --json reviewDecision,statusCheckRollup,...) already exposes in one compact call per repo. An automation agent using only the current MCP tools had to make one list_pull_requests call plus 2 pull_request_read calls per PR just to get this same information, and the resulting accumulated context (~215KB across ~80 calls for 36 PRs) was enough to make the agent's next reasoning step time out. Exposing these two fields directly on the listing/search tools would remove the need for that fan-out entirely for this class of use case.
- 主要語言
- Go
- 星號
- 33.3k
- 分支
- 5.1k
- 平均合併
- 22 小時 46 分鐘
- 30 天內合併 PR
- 17
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/github-mcp-server 的其他 Issue
-
pull_request_read drops merge_commit_sha可能已有人在做 @thejdubb02 於 29 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 84/100
github/github-mcp-server#3235 · 1 則留言 ·
維護者通常 1 天內回覆
-
Add guidance on GitHub autolinked reference formatting for AI agents可能重新可做 關聯的 PR 已關閉且未合併。 未關閉enhancement
難度 1/5 1 小時以內 新手友好度 88/100
github/github-mcp-server#3042 · 2 則留言 ·
維護者通常 1 天內回覆
-
Incorrect install documentation leads to error "error: unknown option '-e'"可能已有人在做 @syf2211 於 58 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
github/github-mcp-server#3032 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
github/github-mcp-server#2803 · 1 則留言 ·
維護者通常 1 天內回覆
-
get_discussion and get_discussion_comments accept calls with missing required parameters instead of returning a validation error可能已有人在做 @rodboev 於 108 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
github/github-mcp-server#2740 ·
維護者通常 1 天內回覆
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
status:approved type:bug
難度 2/5 1-3 小時 新手友好度 85/100
Gentleman-Programming/gentle-ai#5326 ·
維護者通常 1 天內回覆
-
area/testing kind/cleanup priority/backlog triage/accepted
難度 2/5 1-3 小時 新手友好度 78/100
lexfrei/cloudflare-tunnel-gateway-controller#999 ·
維護者通常 1 天內回覆
-
automation models
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
Can the search results with Year Released be in enclosed in the ( ) like Movie/TV(Year Released)未關閉
難度 2/5 1-3 小時 新手友好度 85/100
Dhairya3391/kari#32 ·