GitHub is gradually rolling out shared Copilot Automations for team workflows
Shared Copilot Automations allow teams to create and manage automations together. The feature is being rolled out gradually across five plans. For automations to run in an organization repository, an administrator must enable the policy allowing billing to the organization.
GitHub is gradually rolling out shared Copilot Automations, which allow teams to create and maintain workflows together. According to GitHub, automations combine prompts, triggers and tools, and run autonomously in the cloud using only permitted tools. Previously, personal automations could only be viewed and edited by their creator and used that person's identity and AI credits.
The rollout covers the Copilot Pro, Pro+, Max, Business and Enterprise plans; availability may vary during the rollout. Once the feature is available, automations can be created in any repository to which the user has write access. For a shared automation to run in an organization repository, an administrator must enable the “Allow use of Copilot cloud agent billed to the organization” policy.
A shared automation can be created on github.com, in the GitHub Copilot app or in Visual Studio Code by selecting Shared in the Type field. The automation type cannot be changed after creation.
Why it matters
Other members can also take over maintenance of a workflow that the whole team depends on. When setting it up, however, you need to decide in advance whether to use the personal or shared type and ensure the appropriate billing settings are in place for an organization repository.
Two audiences, two different impacts
What this means
For individuals
When creating an automation for colleagues, you must select the shared type at the outset; it cannot be changed later.
For a business
A company can distribute the management of team automations among multiple people. Running them in organization repositories requires the policy allowing billing to the organization to be enabled.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.