A useful automation becomes fragile when only its creator can maintain it. GitHub’s October 28 update begins rolling out shared Copilot Automations, connecting ownership, access, and billing to a repository.
People with repository read access can see a shared automation; people with write access can edit it. AI credits are charged to the repository owner, and actions on GitHub are attributed to Copilot. The workflow can continue after the original creator leaves.
The handoff includes permissions and cost
GitHub gives bug reproduction on new issues and investigation of production incidents as examples. A team considering either should first decide which tools the automation may use and who will inspect its output. Shared ownership does not define the desired behavior by itself.
Organization-owned repositories require an administrator to enable the policy allowing Copilot cloud-agent usage billed to the organization. The announcement lists Pro, Pro+, Max, Business, and Enterprise plans, while warning that availability varies during rollout.
Select Shared when creating the automation on GitHub, in the Copilot app, or in VS Code. Its type cannot be changed afterward. Start with a bounded workflow and review its change history before depending on it for a team-wide process.
