Feature Request: High-level helper tools for GitHub Projects V2 (e.g. move_issue_to_column)
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 45/100
研究方向
先閱讀現有的 add_project_item 和 update_project_item_field 工具,以及 issue 提議的參數和查找流程。定義可解析 Projects、Items、Fields 和狀態選項的高階 Project helpers 的範圍和行為,然後驗證產生的工具支援所描述的 issue-to-project 和狀態移動工作流程。
由索引模型根據 Issue 內容生成。
描述
Currently, the github-mcp-server provides lower-level Projects V2 tools such as add_project_item and update_project_item_field.
However, these tools are highly dependent on raw GraphQL Global Node IDs (such as item_id, field_id, option_id, etc.) which are difficult for AI agents to retrieve, resolve, and manage dynamically.
For example, to move an issue (e.g. #42 in repository owner/repo) to a project board (e.g. Project Number 1 / Title "Development") in the "In Progress" status column, an AI agent currently has to perform multiple manual lookups:
- Fetch the project list or ID.
- Fetch the project items to locate the global node ID of the issue item.
- Query the project fields to locate the Status field ID and the specific option ID matching
"In Progress". - Call
update_project_item_fieldwith these raw GraphQL node IDs.
This is highly error-prone, requires multiple API round-trips, and makes Projects integration fragile for AI agents.
Proposed Feature:
We would love to see high-level wrapper tools that automate these lookups. For example:
-
add_issue_to_project:- Parameters:
project_number(int) orproject_id(string)repository_owner(string)repository_name(string)issue_number(int)
- Behavior: Automatically resolves the issue's global node ID and adds it to the specified project.
- Parameters:
-
move_project_item(orupdate_project_item_status):- Parameters:
project_number(int) orproject_id(string)repository_owner(string)repository_name(string)issue_number(int) (orpull_request_number/item_id)status_name(string, e.g."In Progress","Done")
- Behavior: Under the hood, resolves the item ID, finds the Project's "Status" field ID, finds the option ID matching the string
status_name, and performs the update.
- Parameters:
These higher-level helper tools would make Projects V2 management significantly easier and more robust for AI agents using the Model Context Protocol.
- 主要語言
- Go
- 星號
- 33.1k
- 分支
- 5k
- 平均合併
- 2 天 3 小時
- 30 天內合併 PR
- 18
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/github-mcp-server 的其他 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
github/github-mcp-server#3235 ·
-
enhancement
難度 1/5 1 小時以內 新手友好度 88/100
github/github-mcp-server#3042 · 2 則留言 ·
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
github/github-mcp-server#3032 · 1 個 reaction ·
-
難度 2/5 1-3 小時 新手友好度 74/100
github/github-mcp-server#2803 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 76/100
github/github-mcp-server#2740 ·
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
agentic-workflows
難度 2/5 1-3 小時 新手友好度 76/100
-
agentic-workflows
難度 2/5 1-3 小時 新手友好度 70/100
microsoft/agent-framework-go#1179 ·
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
-
[Bug]: OLLAMA_KEEP_ALIVE="5m" / "24h" crashes Ollama embedding and vision models with ValueError 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
infiniflow/ragflow#20223 · 1 個 reaction ·
-
bug needs triage pkg/translator/faro
難度 2/5 1-3 小時 新手友好度 88/100
open-telemetry/opentelemetry-collector-contrib#51484 · 1 則留言 ·