Add merge queue support to pull request tools (enqueue, dequeue, queue status)

未關閉
  • 哪裡不對？
#3,669 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
52/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
go, graphql
領域
api, backend-api-design

研究方向

Start by reading the existing pull request tool definitions and their GraphQL request patterns, then check how pull_request_read exposes PR data. Implement the two queue mutations and the status read using the fields listed in the issue. Done means all three operations return the specified queue data, including a clean null when no queue exists; the issue does not name specific files or tests.

由索引模型根據 Issue 內容生成。

描述

enhancement tool-proposal
Describe the feature or problem you'd like to solve

There is no way to interact with a branch's merge queue through the MCP server.

merge_pull_request calls the REST merge endpoint. On a base branch protected by a merge queue ruleset, GitHub rejects that call: the only supported path is to enqueue the pull request and let the queue merge it. Today an MCP client has to fall back to gh pr merge --auto or raw GraphQL for that step, which breaks the MCP-first workflow.

This request is intentionally separate from auto-merge (#2411). Auto-merge is a per-PR flag that merges once requirements pass. A merge queue is a branch-level mechanism with its own queue entries, ordering, and state. They use different GraphQL mutations and should be modelled as different tools, even though a client may use both.

Proposed solution

Add merge queue support to the pull_requests toolset:

  1. enqueue_pull_request (write), wrapping enqueuePullRequest

    • owner, repo, pullNumber (required)
    • jump (optional, boolean): place the entry at the front of the queue
    • expectedHeadSha (optional): maps to expectedHeadOid, mirrors the existing merge_pull_request safety parameter
    • Returns the created merge queue entry: position, state, enqueued time, and the solo/jump flags

  2. dequeue_pull_request (write), wrapping dequeuePullRequest

    • owner, repo, pullNumber (required)
    • Returns the removed entry

  3. get_merge_queue_status method on pull_request_read (read), exposing the PR's mergeQueueEntry

    • Returns whether the PR is queued, its position, state (QUEUED, AWAITING_CHECKS, LOCKED, MERGEABLE, UNMERGEABLE), and the estimated time to merge if available
    • Returns null cleanly when the base branch has no merge queue, so clients can decide between merge_pull_request and enqueue_pull_request

Benefits: agents can complete the full PR lifecycle on repositories that require a merge queue without leaving MCP, and can report queue progress back to the user.

Example prompts or workflows (for tools/toolsets only)
  1. "Add PR #XXX to the merge queue once it is approved."
  2. "Is PR #XXX in the merge queue? What position is it in and is anything blocking it?"
  3. "Remove PR #XXX from the merge queue, I need to push a fix first."
  4. "For every approved PR of mine in this repo, enqueue it if the base branch uses a merge queue, otherwise merge it directly."
  5. "This hotfix is urgent, enqueue it at the front of the queue."
Additional context
  • The two mutations are the same ones used by the gh CLI and the web UI, so the semantics are already familiar to users.
  • merge_pull_request could additionally return a clearer error when the base branch requires a merge queue, pointing the client to enqueue_pull_request. That is a nice-to-have on top of the three items above.
  • Merge queue state is currently readable only indirectly, via the merge_queue rule in governance ruleset output. That tells a client the queue exists, but not whether a given PR is in it.
主要語言
Go
星號
34.2k
分支
5.3k
平均合併
5 天 18 小時
30 天內合併 PR
13

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

github/github-mcp-server 的其他 Issue

查看 github/github-mcp-server 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。