The News, Explained
On November 6, GitHub announced general availability for the @GitHub integration in Slack and Microsoft Teams. Mention the GitHub app in a conversation and you can ask Copilot to investigate a problem or change code. Copilot cloud agent carries out the request in a remote GitHub work environment. It can create issues, which track tasks or problems, and pull requests, which ask reviewers to approve a proposed code change. Source Source Source
The canvas in Teams is a work area beside the conversation for reviewing plans, code changes and previews. Teammates can add context in the chat while looking at the same proposed change. GitHub also says @GitHub can now identify the repository from a message and start a session. A repository is where a project keeps its files and change history. The descriptions of issues and pull requests created by @GitHub identify Slack or Teams as the conversation where the work started. Source Source
The September 25 public preview update expanded the context Copilot could use: supported files and message links in Slack, and embedded images, forwarded messages and thread history in Teams. GitHub said then that Copilot checked for similar issues before creating one and provided a link from the task back to its source conversation. A model chosen mid-conversation could stay in use through the rest of the chat, and Slack gained settings for a default assignee and repository. GitHub also improved progress reporting and reconnection for longer tasks. At the time, the preview was limited to Copilot Business and Enterprise organizations, usage counted against their existing Copilot allowances, and some features were rolling out gradually. Source
Under the current instructions, the GitHub app needs to be installed in Slack or Teams and connected to a GitHub account. Agent sessions require a paid Copilot plan. To start or steer work, you need write access to every repository selected for the session. Organization and enterprise owners can turn off the policy that allows agent work. GitHub says both integrations run sessions in a cloud sandbox, an isolated remote work environment, without requiring a separate sandbox setting. Source Source Source Source
OYOPICK’s Take
Automatic repository selection can make it easier to move from discussion to code. When a thread names several projects, it helps to review the repository and planned scope first. Imagine a conversation about the same error in two services: the Teams canvas gives reviewers a place to read the plan and see which service’s code would change. We hope the attribution and the link to the original thread preserve the context people need to make that call. Source Source Source