본문으로 건너뛰기
AI NEWS JOURNAL
GitHub Copilot 변경 기록AI NEWS / JOURNAL

Copilot Automations로 팀을 위한 공유 워크플로를 구축하세요

공유 Copilot 자동화 기능이 출시되어, 팀원들이 함께 AI 기반 워크플로를 구축하고 유지할 수 있게 되었습니다. Copilot 자동화를 사용하면 프롬프트, 트리거 및 도구를 결합하여…에 맞춘 워크플로를 설계할 수 있습니다. 이 글은 “Copilot 자동화로 팀을 위한 공유 워크플로를 구축하세요”라는 제목으로 GitHub 블로그에 처음 게재되었습니다.

번역 서비스가 일시 중지되어 원문을 표시합니다.

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.

How shared automations work

Visible to your team: Everyone with read access to the repository can see a shared automation, and anyone with write access can edit it.

Billed to the repository owner: AI credits are billed to the organization or user that owns the repository, rather than to the person who created the automation.

Act as Copilot: Actions on GitHub are attributed to Copilot, rather than to any one user.

Built to last: Shared automations belong to the repository, so they keep running if the person who created them leaves the team. Change history lets your team see 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.

Create a shared automation

When you create an automation on github.com, the GitHub Copilot app , or Visual Studio Code, choose Shared under Type. You can’t change an automation’s type after you create it. To learn more, see personal and shared automations.

Shared Copilot Automations are rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans. Availability may vary as the rollout progresses. Once available, you can create automations in any repository where you have write access.

Join the discussion within GitHub Community.

The post Build shared workflows for your team with Copilot Automations appeared first on The GitHub Blog.

자료 출처

원문 읽기 ↗

관련 주제

← 전체 소식 이어 읽기