GitHub Copilot: Shared Automations for Team Workflows
GitHub CopilotGitHub introduced shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of each developer owning their own. An automation combines a prompt, triggers and allowed tools, and Copilot runs it autonomously in the cloud. Shared automations are visible to anyone with read access, editable by anyone with write access, and billed to the repository owner.
Key Takeaways
- Shared automations belong to the repository, so workflows keep running even when their creator leaves the team.
- Each automation combines a prompt, triggers and an allowlist of tools, and Copilot runs it autonomously in the cloud.
- Anyone with read access can view and anyone with write access can edit a shared automation, which makes team maintenance straightforward.
- AI credits are billed to the repository owner, not the creator, which changes cost planning for teams.
- Actions are attributed to Copilot rather than an individual, keeping activity history clear.
- Organization admins must enable the "Allow use of Copilot cloud agent billed to the organization" policy, and the "Shared" type cannot be changed after creation.
Automations that belong to the team
GitHub extended Copilot Automations with a new Shared type. An automation is a combination of a prompt, one or more triggers and a set of permitted tools. Copilot runs it autonomously in the cloud and uses only the tools the automation allows. Until now, automations were tied to the person who created them. Shared automations instead belong to the repository, so a whole team can build, review and maintain them in one place.
GitHub gave several examples of what such workflows can do: reproduce a bug as soon as an issue is opened, capture screenshots when a pull request is marked ready for review, or investigate a production incident when monitoring detects it.
Visibility, editing and history
A shared automation can be seen by anyone with read access to the repository, and edited by anyone with write access. Because the automation is a repository asset rather than a personal one, it keeps running if the person who created it leaves the team. A change history shows how the automation has evolved over time, which helps teams review and trust the behavior of workflows that run without supervision.
Billing and attribution
Shared automations change who pays and who is credited. AI credits consumed by a shared automation are charged to the owner of the repository, whether that is an organization or a user, rather than to the creator. Actions taken by the automation are attributed to Copilot instead of an individual developer.
Setup and availability
Users choose "Shared" as the type when creating an automation. The type cannot be changed afterward, so teams should decide up front whether a workflow is personal or shared. For shared automations to run in organization-owned repositories, an organization administrator must enable the policy "Allow use of Copilot cloud agent billed to the organization".
The feature is rolling out to Copilot Pro, Pro+, Max, Business and Enterprise users, and availability varies during the rollout.