Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Feature Request: High-level helper tools for GitHub Projects V2 (e.g. move_issue_to_column)

未關閉
#2,603 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
45/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
github, go, graphql
領域
api, tooling

研究方向

先閱讀現有的 add_project_item 和 update_project_item_field 工具,以及 issue 提議的參數和查找流程。定義可解析 Projects、Items、Fields 和狀態選項的高階 Project helpers 的範圍和行為,然後驗證產生的工具支援所描述的 issue-to-project 和狀態移動工作流程。

由索引模型根據 Issue 內容生成。

描述

request ai review

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:

  1. Fetch the project list or ID.
  2. Fetch the project items to locate the global node ID of the issue item.
  3. Query the project fields to locate the Status field ID and the specific option ID matching "In Progress".
  4. Call update_project_item_field with 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:

  1. add_issue_to_project:

    • Parameters:
      • project_number (int) or project_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.
  2. move_project_item (or update_project_item_status):

    • Parameters:
      • project_number (int) or project_id (string)
      • repository_owner (string)
      • repository_name (string)
      • issue_number (int) (or pull_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.

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

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/github-mcp-server 的其他 Issue

查看 github/github-mcp-server 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。