# GitHub — Build shared workflows for your team with Copilot Automations

- Company: GitHub (github.com)
- Announced: 2026-10-28T15:35:00+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://github.blog/changelog/2026-10-28-build-shared-workflows-for-your-team-with-copilot-automations
- Record: https://forck.live/items/28835-build-shared-workflows-for-your-team-with-copilot-automations
- Subject: Copilot

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.

## Evidence

Verbatim from https://github.blog/changelog/2026-10-28-build-shared-workflows-for-your-team-with-copilot-automations:

> Shared Copilot Automations are rolling out, enabling teams to build and maintain AI-powered workflows together.
> 
> With Copilot Automations, you can combine prompts, triggers, and tools to design workflows around the way your team works. Copilot runs autonomously in the cloud, using only the tools you’ve allowed. For example, you could create automations to:
> 
> Reproduce bugs as soon as an issue is opened.
> 
> Capture screenshots of the changes when a pull request is marked as ready.
> 
> Automatically investigate production incidents as soon as they’re detected in your monitoring tool.
> 
> Until now, automations have been personal, meaning only you could see and edit them, and they used your identity and AI credits. That works well for automating your own work, like drafting your standup updates, but not for workflows your whole team relies on. Shared automations let your team build and maintain those workflows together.
> 
> Visible to your team : Everyone with read access to the repository can see a shared automation, and anyone with write access can edit it.

---

Record: https://forck.live/items/28835-build-shared-workflows-for-your-team-with-copilot-automations
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md