官方更新 GitHub Changelog Fri, 21 Aug 2026 正文 ok 460 words

Slack 中全新的 GitHub Copilot 体验

英文标题:The new GitHub Copilot experience in Slack

GitHub 面向 Slack 推出公开预览版集成,将 GitHub Copilot CLI 和 GitHub Copilot app 的代理能力带入团队对话。开发者可通过在私信、频道或话题中提及 `@GitHub`,让 Copilot 回答代码问题、处理 Issue、调查故障、实现变更并创建 Pull Request。GitHub 还是 Slack Code 的首发合作伙伴,后者是一种专为 Agent 设计的频道类型,可让团队公开协作、审查计划和代码差异。该预览版面向 GitHub Copilot Business 与 GitHub Copilot Enterprise 组织开放,使用量计入现有 Copilot 权益及云端 Agent 预算。
打开原文相关 3 · 机会 3
media170.8 KB media183.8 KB

中文

Slack 中的 GitHub 集成现已在公开预览阶段,将 GitHub Copilot CLI 和 GitHub Copilot app 的代理能力带入 Slack。你可以与 @GitHub 协作,规划变更、调查问题,并从团队协调工作的对话中交接编码任务。GitHub 还是 Slack Code 的首发合作伙伴;Slack Code 是一种专为 Agent 设计的新型频道。

将 Copilot 引入对话流程,可帮助团队把共同意图转化为可交付的工作成果。

在私信、频道或话题中提及 @GitHub,即可启动一个 Agent 会话。Copilot 可以利用对话内容和已获许可的 GitHub 上下文执行以下操作:

  • 回答有关你的代码和 GitHub 活动的问题。
  • 分类处理 Bug 报告、更新现有 Issue,或创建并标记新的 Issue。
  • 调查故障、实现变更,并在安全的云端沙盒中验证其工作。
  • 创建 Pull Request,并提供指向该对话的链接以供审查。

当你在开会、通勤或专注于其他工作时,GitHub Copilot 仍会异步持续工作。它执行任务期间,你可以通过 Slack 引导该会话;随后也可以在终端、GitHub Copilot app 或 IDE 中从该 Pull Request 继续工作。

GitHub Copilot 还可以创建专用代码频道,让任务保持聚焦,同时不会给原始对话增加噪声。

在代码频道内,团队可以跟进计划、检查代码差异、审查诸如 HTML 产物等输出预览,并与 Copilot 迭代协作。任何人都可以从原始话题加入该频道、补充上下文、调整实施方向或停止会话。

Slack 中的 Agent 会话是共享的,因此团队可以在请求最初发起的位置协作处理工作,而不是由某一个人与 Agent 私下协作。

公开协作也让高效的 Agent 工作流更容易被学习。开发者可以看到队友如何向 Agent 提示,并相互学习。从对话中创建的 Issue 和 Pull Request 将归属于 Copilot app 身份,而所有操作仍受现有 GitHub 权限和控制机制的约束。

该公开预览版面向使用 GitHub Copilot Business 和 GitHub Copilot Enterprise 套餐的组织开放。使用量将计入你现有的 Copilot 权益,并可通过现有 Copilot 云端 Agent 预算进行管理。

开始使用:

  1. 确保管理员已为你的组织启用 Copilot 云端 Agent 策略。
  2. 安装或升级 GitHub app for Slack。
  3. 关联你的 GitHub 账户,并在对话中提及 @GitHub。

仓库管理员可以要求:任何归属于 Copilot app 身份的 Pull Request 在合并前,必须额外获得一次批准。要求额外批准可确保由 Agent 编写的工作在发布前仍有人类参与审核。团队能够快速推进,同时不会失去合规监督。

有关设置详情和支持的工作流,请参阅如何通过 Slack 使用 Copilot coding agent。

English / 原文

The GitHub integration in Slack now brings the agentic capabilities of GitHub Copilot CLI and the GitHub Copilot app into Slack in public preview. You can work with @GitHub to plan changes, investigate problems, and hand off coding tasks from the conversations where your team coordinates work. GitHub is also a launch partner for Slack Code, a new type of channel designed for agents.

Bringing Copilot into the flow of conversation helps your team turn shared intent into shippable work.

Mention @GitHub in a direct message, channel, or thread to start an agent session. Copilot can use the conversation and permitted GitHub context to:

  • Answer questions about your code and GitHub activity.
  • Triage bug reports, update existing issues, or create and label new issues.
  • Investigate failures, implement changes, and validate its work in a secure cloud sandbox.
  • Open a pull request and provide a link to the conversation for review.

GitHub Copilot continues working asynchronously while you’re in a meeting, commuting, or focused on something else. You can direct the session from Slack as it works, then continue from the pull request in your terminal, the GitHub Copilot app, or your IDE.

GitHub Copilot can also create a dedicated code channel that keeps the task focused without adding noise to the original conversation.

Inside the code channel, your team can follow the plan, inspect the diffs, review output previews like HTML artifacts, and iterate with Copilot. Anyone can join the channel from the original thread, add context, redirect the approach, or stop the session.

Agent sessions in Slack are shared, so your team can collaborate on the work where the request began instead of one person working privately with an agent.

Working in the open also makes effective agent workflows easier to learn. Developers can see how their teammates prompt the agent and learn from each other. Issues and pull requests created from the conversation are attributed to the Copilot app identity, and actions remain bounded by existing GitHub permissions and controls.

The public preview is available to organizations on GitHub Copilot Business and GitHub Copilot Enterprise plans. Usage counts against your existing Copilot entitlements and can be managed with existing Copilot cloud agent budgets.

To get started:

  1. Make sure an administrator has enabled the Copilot cloud agent policy for your organization.
  2. Install or upgrade the GitHub app for Slack.
  3. Link your GitHub account and mention @GitHub in a conversation.

Repository administrators can require an additional approval for any pull request attributed to the Copilot app identity before it can merge. Requiring an additional approval keeps a human in the loop before agent-authored work ships. Your team moves fast without losing compliance oversight.

For setup details and supported workflows, see how to use Copilot coding agent with Slack.