As of the October 23, 2026 Changelog entry, GitHub describes a consolidated GitHub app in Teams—previously called GitHub notifications—that connects inbound alerts to Copilot. The flow it spells out is short: a bug report arrives in Teams; @github investigates, fixes, and creates a pull request; the team reviews, tests, and merges.
You can get notified in channels, group chats, or private chats, then @mention GitHub to turn an update into action. If you already use GitHub notifications, GitHub says to update the app to the latest version so existing notification capabilities keep working. In the consolidated app, mention `@GitHub` and follow prompts to connect your GitHub account and select a repository.
Teams that still rely on the legacy GitHub app need a migration date on the calendar: that app will be renamed “GitHub (deprecated)” and retired on November 16, 2026. GitHub asks those users to install the consolidated GitHub app to keep using Copilot in Teams. Related reading: VS Code 1.143 Makes the Copilot Harness the Default for New Sessions, GitHub Copilot Models List (October 2026), and Simular Agent S4 Evolves Interfaces Without Retraining the Model.
As for how reliably the investigate-fix-PR path works in your org’s Teams tenants, which repositories Copilot can touch after you connect an account, and what breaks if the legacy app is still installed past November 16—we don’t have that information yet. If you’ve tried it, you can send feedback through the site-owner contact link in the footer. A Changelog ship note is not a guarantee that every notification becomes a merge-ready PR.