借助 Copilot Automations 为团队构建共享工作流

共享 Copilot Automations（Copilot 自动化）现已逐步推出，支持团队共同构建和维护由 AI 驱动的工作流。

借助 Copilot Automations，你可以将提示词（prompts）、触发器（triggers）和工具（tools）相结合，围绕团队的工作模式设计专属工作流。Copilot 仅使用你所授权的工具在云端自主运行。例如，你可以创建自动化工作流来实现：

• 在 Issue 提交后立即复现 Bug。
• 当 Pull Request（PR）标记为就绪状态时，自动捕获变更内容的截图。
• 监控工具一旦检测到生产环境事件，立即自动开展排查。

在此之前，自动化都是个人专属的，这意味着只有你能查看和编辑它们，且它们消耗的是你的个人身份和 AI 配额（credits）。这种模式非常适合用来实现个人工作的自动化（比如起草站会更新），但并不适用于整个团队依赖的公共工作流。共享自动化则让团队能够共同构建和维护这些工作流：

• 对团队可见（Visible to your team）：任何拥有代码仓库读取权限的成员均可查看共享自动化，拥有写入权限的成员则可对其进行编辑。
• 计费归属仓库所有者（Billed to the repository owner）：AI 配额将由拥有该仓库的组织或用户承担，而非自动化创建者个人。
• 以 Copilot 身份执行（Act as Copilot）：在 GitHub 上的操作归属于 Copilot，而非任何单一用户。
• 持久可用（Built to last）：共享自动化从属于代码仓库，因此即使创建者离职，工作流依然会持续运行。变更历史记录可以让团队随时查看工具、触发器和提示词的演进过程。

若要在组织拥有的代码仓库中运行共享自动化，管理员必须先启用“允许使用由组织计费的 Copilot 云端 Agent”（Allow use of Copilot cloud agent billed to the organization）策略。

当你在 github.com、GitHub Copilot 应用或 Visual Studio Code 中创建自动化时，在 Type（类型）下选择 Shared（共享）。请注意，自动化创建后无法更改其类型。了解更多信息，请参阅个人与共享自动化。

共享 Copilot Automations 正在面向 Copilot Pro、Pro+、Max、Business 和 Enterprise 方案的用户分批推出。具体可用时间可能因灰度发布进度而异。功能生效后，你可以在拥有写入权限的任何代码仓库中创建自动化。

欢迎在 GitHub Community 参与讨论。

Shared Copilot Automations are rolling out, enabling teams to build and maintain AI-powered workflows together.

With Copilot Automations, you can combine prompts, triggers, and tools to design workflows around the way your team works. Copilot runs autonomously in the cloud, using only the tools you’ve allowed. For example, you could create automations to:

• Reproduce bugs as soon as an issue is opened.
• Capture screenshots of the changes when a pull request is marked as ready.
• Automatically investigate production incidents as soon as they’re detected in your monitoring tool.

Until now, automations have been personal, meaning only you could see and edit them, and they used your identity and AI credits. That works well for automating your own work, like drafting your standup updates, but not for workflows your whole team relies on. Shared automations let your team build and maintain those workflows together.

• Visible to your team : Everyone with read access to the repository can see a shared automation, and anyone with write access can edit it.
• Billed to the repository owner : AI credits are billed to the organization or user that owns the repository, rather than to the person who created the automation.
• Act as Copilot : Actions on GitHub are attributed to Copilot, rather than to any one user.
• Built to last : Shared automations belong to the repository, so they keep running if the person who created them leaves the team. Change history lets your team see how the tools, triggers, and prompt have evolved.

For shared automations to run in an organization-owned repository, an administrator must enable the “Allow use of Copilot cloud agent billed to the organization” policy.

When you create an automation on github.com, the GitHub Copilot app , or Visual Studio Code, choose Shared under Type. You can’t change an automation’s type after you create it. To learn more, see personal and shared automations.

Shared Copilot Automations are rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans. Availability may vary as the rollout progresses. Once available, you can create automations in any repository where you have write access.

Join the discussion within GitHub Community.