From the source
GitHub is rolling out shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of keeping them personal.
- Until now, automations were personal, meaning only the creator could see and edit them, and they used that person's identity and AI credits.
- Shared automations are visible to everyone with read access to the repository, and anyone with write access can edit them.
- AI credits are billed to the organization or user that owns the repository rather than to the person who created the automation, and actions on GitHub are attributed to Copilot rather than to any one user.
- Shared automations belong to the repository, so they keep running if the creator leaves the team, and change history shows 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.
- The feature is rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans, and availability may vary as the rollout progresses.
