Insiders Feedback: PRECISE file patching and multiple toolsets in the URL
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, go
调研方向
Start by locating the server-side implementations of create_or_update_file and push_files, then trace how remote-connector URLs parse toolset and header options. The issue does not identify files or tests, so scope the patch format, blob-SHA conflict handling, and URL syntax before implementation. Done means a requested exact or unified diff applies safely against the specified blob and conflicting changes are rejected, while the URL can select a bounded set of toolsets.
由索引模型根据 Issue 内容生成。
描述
Version: Insiders
Feature: PATCHES ; CUSTOM HEADERS
Feedback:
Two things from daily use through a remote connector:
-
Precise patching Right now changing one line means pushing the whole file back through
create_or_update_file/push_files. For a 200KB doc that's a lot of tokens to add a comma, and a long rewrite through a model is an easy way to corrupt the file. Try add one line to ~MB .ts file. A patch tool would fix it: either old/new string replacement (must match exactly once) or a unified diff, applied server-side against a given blob SHA, rejected on conflict. -
Toolset selection in the remote URL The default toolset is too weak, and
x/allis too big xd
every tool schema eats context on each request. I'd like to pick a few toolsets in the URL itself (e.g repos + pull_requests + actions), remote connector config can't set custom headers.
Win & Win situation: a one-line edit to a large file costs roughly the size of the diff, and one connector URL exposes selection of tools instead of all of them.
LESS BANDWIDTH MORE EFFICIENCY
- 主要语言
- 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
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
open-feature/flagd-schemas#237 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
superplanehq/superplane#9234 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
betterleaks/betterleaks#469 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
prime-radiant-inc/evener#5901 ·
维护者通常 1 天内回复