Insiders Feedback:
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by tracing the action tool call and its confirmation flow in the GitHub MCP Server; the issue does not name source files or tests. Reproduce PR creation in Copilot chat and follow what happens after Allow, including the second confirmation and whether the agent continues. Done means one approval creates the PR and the agent continues automatically.
由索引模型根据 Issue 内容生成。
描述
Version: 1.140.0
Commit: 07f806f999227108933c2e30515b26eecc1fda74
Date: 2026-09-30T10:38:38+02:00
Electron: 43.7.3
ElectronBuildId: 15386805
Chromium: 150.0.7871.250
Node.js: 24.21.0
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.89-7
@github/copilot-sdk: 1.0.15-preview.4
OS: Linux x64 7.0.0-38-generic
Feature: The UI component shown for action tool calls like PR create
Feedback:
I like the idea of an in-chat UI for action tool calls, but right now it conflicts with the normal flow. Here's what I see in Copilot chat:
-
Tool calls aren't auto-approved, so the PR details are already visible in the confirmation prompt. The UI isn't great, but it's enough for a quick review of the PR create request. When I click Allow, the original tool call appears to be cancelled and shows an ✗ mark.
-
A new UI then appears, asking me to confirm all the same details again. I have to approve a second time by clicking the Create PR button.
-
Once that's done, the chat stops, and I have to ask the AI to continue. Previously, a single Allow was all it took and everything just worked.
Expected behavior: a single approval step, with the agent continuing automatically afterward.
Thanks for looking into this. I hope it gets resolved soon.
- 主要语言
- Go
- 星标
- 34.2k
- 派生
- 5.3k
- 平均合并
- 5 天 18 小时
- 30 天内合并 PR
- 13
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/github-mcp-server 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 69/100
github/github-mcp-server#3760 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
github/github-mcp-server#3758 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
github/github-mcp-server#3729 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
github/github-mcp-server#3722 ·
维护者通常 2 天内回复
-
Insiders Feedback: PR created UI doesn't link to the PR可能已有人在做 @genius-0963 于 5 天前认领。 未关闭bug insiders user-experience
难度 2/5 1-3 小时 新手友好度 65/100
github/github-mcp-server#3658 ·
维护者通常 2 天内回复
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
prime-radiant-inc/evener#5901 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
-
kind/bug
难度 2/5 1-3 小时 新手友好度 78/100
kyma-project/serverless#2769 ·
维护者通常 1 天内回复
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 78/100
hexlet-basics/hexlet-basics#962 ·
维护者通常 1 天内回复
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransport可能已有人在做 @dejanstrbac 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复