push_files / create_or_update_file have no way to write large content without inlining it in the tool call
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the implementations of push_files and create_or_update_file, then trace how file content is serialized into GitHub API calls. Compare the available blob, tree, and commit operations described in the issue and check whether the server exposes any existing streaming or upload pattern. Done means callers can write large files without sending all content inline, or have a documented supported size ceiling.
由索引模型根据 Issue 内容生成。
描述
push_files and create_or_update_file require the full file content inline in the tool call, with no option for a file-by-reference upload or chunked/streaming write for large files.
Repro:
- Call
push_fileswith one file whose content is on the order of 2-3 MB of text. - The call either fails or risks truncation because the entire content must be serialized into the tool call's JSON payload.
Expected: some way to push large files without having to pass the complete content inline in a single call, e.g. a multipart/chunked write, or accepting a pre-uploaded blob SHA (the REST API's own git blob + tree + commit flow would allow this, but there is no MCP tool here that exposes creating a blob from a stream or from a size that exceeds a reasonable tool-call payload).
Actual: the only way to commit large text content through this MCP server is to pass it whole inline, which breaks down well before typical repo file sizes (multi-MB text exports, long logs, etc.).
Ask: expose a way to create a blob/commit for large content without it having to round-trip through a single tool call's inline payload, for example a tool that accepts a local-file-style streamed upload, or document a supported size ceiling so callers know when to split rather than discovering it empirically.
- 主要语言
- 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 天内回复