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

Đang mở
  • Có gì không ổn?
#3,669 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 2 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
52/100
Loại issue
Tính năng
Độ rõ ràng
Đặc tả rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
go, graphql
Lĩnh vực
api, backend-api-design

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.
Ngôn ngữ chính
Go
Star
34.2k
Fork
5.3k
Merge trung bình
5 ngày 18 giờ
Pull request đã merge (30 ngày)
13

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của github/github-mcp-server

Tất cả issue của github/github-mcp-server

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.