GitHub announced the rollout of shared Copilot Automations on October 28. A team can combine prompts, triggers, and allowed tools in repository workflows that are visible and maintainable by more than their original creator.

What changes for a team

  • Readers of the repository can see a shared automation, while contributors with write access can edit it.
  • AI credit usage is charged to the repository owner, and GitHub actions are attributed to Copilot.
  • The automation remains with the repository if its creator leaves, with a history of how its configuration changed.

GitHub describes possible workflows such as reproducing a newly reported bug or collecting a screenshot when a pull request is ready. Organization-owned repositories require an administrator policy, and availability is rolling out across eligible plans.

Review permissions, tools, billing, and the official availability guidance before making an automation part of a team's critical process.