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

[Tracking] Copilot SDK v2.0

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

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
20/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍

研究方向

首先檢視原生子 issue 以及歷史 issue #1934、#1930、#1976、#2048、#2202、#2395、#2463 和 #2505;此處未指定任何實作檔案或測試。將每個變更集對應至其所需的 API、執行階段、可靠性和遷移工作。只有在每個計畫項目都已實作、解決或明確重新評估,並且具備整合測試、遷移文件和獲核准的發行計畫時,才算完成。

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

描述

sdk-v2

Goal

Deliver the API, runtime integration, reliability, and migration work required for Copilot SDK v2.

The work carried forward from #1934 represents maintainer intent: these are jobs we expect to do for v2, not an open-ended list of ideas for contributors or agents to accept or reject independently.

Scope and presumption

The native sub-issues group the historical work into coherent change sets. Work listed in them should be implemented unless current investigation produces concrete new information that changes the situation, for example:

  • the work has already been completed or made obsolete
  • the proposed implementation no longer fits the current architecture
  • a required change belongs partly or wholly in another repository
  • a newly discovered compatibility, feasibility, or product constraint warrants reconsideration

When that happens, document the evidence and proposed change of direction on the relevant issue. Do not drop, defer, or close planned work merely because another approach seems preferable. A maintainer should confirm any decision not to deliver an item that was carried forward from #1934.

Work that requires github/copilot-cli changes remains part of the intended outcome until the dependency is explicitly reconsidered. Create or link the corresponding runtime work rather than treating the repository boundary as an automatic reason to omit it.

This tracker concerns the SDK package major version. It does not track SDK-to-CLI wire protocol v2.

Working agreement

  • Investigate each change set enough to implement it correctly and identify existing or external work.
  • Keep breaking v2 pull requests open and based on main until maintainers approve the integration and release plan.
  • Authors may rebase those pull requests independently while main continues to ship v1.
  • Do not merge a breaking v2 pull request into main until maintainers approve the approach.
  • Merge compatible v1 groundwork where it reduces the eventual breaking change without changing supported behavior.
  • If implementation uncovers a reason to change scope, report it with evidence and wait for maintainer direction rather than deciding unilaterally not to proceed.

Release gates

  • Every planned item is implemented, demonstrably already resolved, or explicitly reconsidered by maintainers based on documented new information.
  • The accepted changes are tested together.
  • Maintainers have agreed an integration plan that protects remaining v1 releases.
  • Breaking changes and migrations are documented per SDK.
  • v2 preview and stable release criteria are agreed.

Historical context

  • #1934
  • #1930
  • #1976
  • #2048
  • #2202
  • #2395
  • #2463
  • #2505
主要語言
Java
星號
10.6k
分支
1.5k
PR 合併指標
30 天內沒有已合併 PR

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

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

github/copilot-sdk 的其他 Issue

查看 github/copilot-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

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

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