Ask a Slack administrator to install the GitHub integration, invite the app to the channel and mention @GitHub with a reproducible issue and the full repository name. Connect your GitHub account if prompted, and check Copilot access and repository permissions before assigning code changes. GitHub setup instructions.
On November 6, 2026, GitHub announced general availability of @GitHub in Slack and Microsoft Teams. A team can ask Copilot to investigate a bug, open an issue or prepare a code change from a conversation. To try it, start with a reproducible issue, give the repository's full name and decide in advance who will review the result. [1]
What each platform adds
In Teams, Canvas shows plans, code changes and previews alongside the conversation. That gives the team a place to discuss what should change before reviewing the code in detail. GitHub also describes a shorter path into a coding session when @GitHub identifies the repository from the message. Issues and pull requests it creates include a note identifying the originating platform and user. That note gives reviewers a way to trace the origin of a request. [1]
An example for a maintenance team
Imagine a team sees a report in Slack that the application's search box returns no results for a word with an accent. The request can name the repository and include a sample input, the observed result and what should have appeared. If the bug only happens after rebuilding the index, include that step too. The team then has a shared yardstick for judging the investigation and any eventual fix.
I would ask the agent to investigate first and summarise its hypotheses. Someone on the team can check whether the problem lies in search, index preparation or test data. Only then would I decide whether to open an issue or request a change. If the initial response points to the wrong repository, correcting it at that stage keeps the discussion from turning into a patch for a different service.
If the agent opens a pull request, review both the change and its tests. In the search example, the accented word is one useful test, and it is also worth checking the unaccented version and other queries that already worked. That helps distinguish a targeted fix from a change that unintentionally alters general behaviour. The conversation can preserve the reason for the change, and the pull request can record the test results.
Where it is available
The announcement confirms general availability in Slack and Teams and links to entry points for both. It also mentions situations where users have yet to sign in or need access to the app. GitHub's announcement gives no country list, regional timetable or plan-by-plan breakdown for the integration. To check actual access, see whether @GitHub is enabled in your workspace and whether your account can work with the intended repository. [1]
The first trial is also a chance to measure the cost of review. Record how long it takes the team to turn the conversation into a reproducible issue and how often someone has to correct the context. If reconstructing the bug still takes the most time, a better documented request may help more than adding automation. Test the workflow with one well understood issue before using it for a change that touches several services or needs multiple teams to approve it.
If the report comes from a busy channel, agree which parts of the thread belong in the issue. A link can help those with access, while a self-contained description lets people who missed the conversation reproduce the bug. Before ending the trial, ask someone else to follow the issue steps without reading the thread. If they can reproduce the bug, the team has a useful record even if it ultimately implements the fix through another workflow.
What can @GitHub do in Slack and Teams?
It can investigate bugs, create issues, prepare code changes and open pull requests from chat.