Dashboard

GitHub Copilot in Teams Turns Chat Alerts Into PRs

GitHub announced on 23 October that its Teams app now pairs notifications with Copilot, so a mention in chat can investigate a bug and open a pull request.

Cecilia Iona
Cecilia Iona
Senior Editor, AI & Product
24 October 20261 min read

GitHub Copilot in Teams is a GitHub app for Microsoft Teams that lets you mention @GitHub in a chat, have Copilot investigate an issue, and get a pull request back without leaving the conversation. GitHub announced it in a changelog entry dated 23 October 2026.

What GitHub announced

The new app combines GitHub notifications with Copilot. You can receive notifications in channels, group chats or private chats, then mention GitHub to act on an update. GitHub's own example has three steps: a bug report arrives in Teams, @github investigates the issue, fixes the bug and creates a pull request, and the team reviews, tests and merges it.

The app was previously called GitHub notifications. Existing users are asked to update to the latest version, and GitHub says current notification features keep working.

How to set it up

The changelog lists four steps:

  1. Install the consolidated GitHub app in Teams.

  2. Mention @GitHub in a channel, group chat or private chat.

  3. Follow the prompts to connect your GitHub account.

  4. Select a repository.

The deadline for the old app

The legacy GitHub app will be renamed "GitHub (deprecated)" and retired on November 16. The changelog does not state the year, but the entry is dated October 2026, so this is the next mid-November. If your team gets alerts through the old app, install the consolidated one before then or those alerts stop.

What the announcement does not say

Several details a team would want before switching it on are missing from the page:

Question

What the changelog says

Does it need a paid Copilot plan?

Not stated

Usage limits

Not stated

Admin or permission requirements

Only that you connect an account and pick a repository

Rollout region or timeline

Not stated

Check the linked GitHub Community discussion and your organisation's Copilot settings before assuming it will work for everyone in the channel.

Why it matters if you are building with AI

A chat message that can end in a pull request moves the review step from "someone opened a PR" to "someone typed a sentence in a channel". That is convenient for a small team, and it also shortens the gap between a vague complaint and a code change.

If you are tracking how fast this area moves, how to keep up with AI news covers a sustainable routine. Two habits keep this safe. First, treat the pull request the same way you would one from any contributor: read the diff, run the tests, and do not merge on the strength of the chat summary. The guide on reviewing an AI agent's diff before merging covers what to look for. Second, decide in advance who may trigger it. In a channel with customers or contractors, a mention should not be a way to start work on your repository.

If an agent does something nobody asked for, here is what to do.

A short pre-install checklist

  • Pick one test repository and one private chat for the first week.

  • Confirm in your GitHub settings which repositories the app can reach.

  • Keep branch protection on, so a Copilot pull request still needs a human approval.

  • Write down who owns the November 16 switch from the old app.

For how this fits the wider tool landscape, see GitHub Copilot compared with Claude Code, and for the previous GitHub dashboard change see the Copilot impact dashboard update.

FAQ

What is GitHub Copilot in Teams?

It is the consolidated GitHub app for Microsoft Teams. It sends GitHub notifications into chats and lets you mention @GitHub so Copilot can investigate an issue and open a pull request.

Does GitHub Copilot in Teams replace the GitHub notifications app?

It is the same app under a new name and with new abilities. The legacy app becomes "GitHub (deprecated)" and is retired on November 16.

Do I need a Copilot subscription to use it?

The changelog does not say. Check the linked community discussion and your GitHub plan before relying on it.

Can it merge code on its own?

The changelog describes Copilot creating a pull request, with the team then reviewing, testing and merging. It does not describe automatic merging.

How did this land?

About the author

Cecilia Iona
Cecilia Iona

Senior Editor, AI & Product

Cecilia leads the Swarmz editorial desk. She has spent a decade turning complex AI and product topics into writing people actually finish, and she owns the blog's quality bar.

Share

Get the next post in your inbox

One email a month. Product updates, engineering posts, and the best of Built with Swarmz.

I agree to receive emails about AI building tips and Swarmz product news. Unsubscribe any time.