GitHub Rolls Out Shared Copilot Automations for Teams
Shared Copilot Automations now allow teams to collaboratively build and maintain AI-powered workflows in repositories. The feature brings visibility, shared maintenance, and improved billing for organizations.
What changed?
GitHub has introduced shared Copilot Automations for users on Copilot Pro, Pro+, Max, Business, and Enterprise plans. Teams can now collaboratively build, view, and edit AI-powered automations within a repository. These automations are visible to everyone with read access and editable by anyone with write access. AI credits are now billed to the organization or repository owner, and shared automations persist beyond individual contributors’ tenure.

Why does it matter to an everyday developer?
Previously, automations were personal and bound to individual users, making team-wide workflow automation difficult to maintain or scale. Now, any developer with write access can create and maintain critical automations, such as automatic bug reproduction or incident investigation, as part of the shared project environment. Actions are attributed to Copilot, improving transparency, and automations continue to run even when their original creator leaves the repository.
What can the developer do now?
Developers can create or contribute to shared Copilot Automations by selecting the Shared type when building automations in GitHub, the Copilot app, or Visual Studio Code, assuming they have write access. Administrators in organizations must enable the policy for shared automations to run in organization-owned repositories. Since automations' type cannot be changed after creation, it is important to decide between personal or shared at setup.
