GitHub Copilot in Teams: Unified notifications, issue-to-pull-request workflow

From a notification conversation to code fixes

The new app incorporates the existing GitHub notifications app. Users receive alerts in Teams channels, group chats, and private chats, then mention GitHub to respond. GitHub says this helps fix issues and ship code faster.

The key change is a shared entry point for notifications and code work. Instead of moving to another conversation or repeating context, developers can start responding in the Teams conversation where the notification arrived.

From issue notifications to pull requests

GitHub outlines three steps. A bug report arrives in Teams. A user mentions GitHub, and Copilot investigates, fixes the bug, and creates a pull request proposing code changes for review. The team then reviews, tests, and merges the fix.

Existing users and teams installing the app

GitHub says teams with the existing GitHub notifications app can keep using its notification features by updating to the latest version.

The legacy GitHub app will be renamed 'GitHub (deprecated)', with support scheduled to end on November 16. Teams using it must install the unified GitHub app to continue using Copilot in Teams.

To start work, mention GitHub in the unified app, follow the prompts to link a GitHub account, and select a repository, the space that stores the project files to work on.

Migration paths depend on the existing app

Migration depends on the installed app, not just Copilot use. GitHub notifications users update to retain alerts. Legacy GitHub app users must switch to the unified app to keep using Copilot as support ends.

GitHub describes shipping code without leaving the conversation as faster, but provides no figures for time savings or measurement conditions.

The value of this update lies in making notifications the starting point for code work while leaving final review and merging to the team.