GitHub rolls out shared Copilot Automations owned by repositories
GitHub announced the rollout of shared Copilot Automations on October 28. Teams can combine prompts, triggers and allowed tools into workflows that run in the cloud. This is a rollout, not a guarantee that every eligible account already has the feature.
The announcement contrasts shared automations with personal automations, which only their creator could see and edit and which used that person's identity and AI credits. A shared automation belongs to its repository and can remain available when its original author leaves a team.
Everyone with read access to a repository can see a shared automation, while people with write access can edit it. Change history records how prompts, triggers and tools evolve. Teams still need to review permissions and workflow changes rather than assume collaboration itself makes an automation safe.
AI credits are billed to the organization or user that owns the repository. Actions on GitHub are attributed to Copilot, rather than to the individual who created the workflow. This changes attribution and billing, not whether the work consumes credits.
An administrator must enable the policy allowing the Copilot cloud agent to run with organization billing before shared automations can run in an organization-owned repository. When creating an automation, users choose its type; GitHub says the type cannot be changed afterward.
Shared automations are rolling out to Pro, Pro+, Max, Business and Enterprise users on github.com, the Copilot app and Visual Studio Code. Once available, creation requires write access to the repository. GitHub's examples include bug reproduction, screenshots and incident investigation, not independently measured reliability or a promise that every incident will be fixed.