Bug reports seldom land in the tool where the fix eventually gets written. A new GitHub app for Microsoft Teams narrows that gap by folding notifications and Copilot into one bot: a developer who spots a problem in a channel, group chat or private chat can summon the assistant with an @GitHub mention and hand it the task. The assistant looks into the reported issue, drafts a fix and opens a pull request, after which the team reviews, tests and merges the change the way it normally would.
GitHub frames the release as a way to keep the discussion and the code in one place rather than shuttling between a chat client and a repository.
The new GitHub app in Teams brings notifications and Copilot together, helping teams turn issues into fixes and ship code faster without leaving the conversation.
The update also fits a wider effort by Microsoft to make Teams a place where work is carried out, not just discussed. Microsoft has indicated that further capabilities aimed at developers and at meeting management are coming to the platform, while making clear that access will vary by user instead of arriving as a single uniform release.
- Key Point: The consolidated GitHub app for Microsoft Teams merges issue notifications with Copilot, triggered when a user mentions @GitHub in a channel, group chat or private chat.
- Key Point: A notification about a defect can become an investigation, a code fix and a pull request without leaving Teams, though human review and merging remain part of the loop.
- Key Point: The previous app is being renamed “GitHub (deprecated)” and retired on November 16, so organizations still relying on it must switch to the consolidated version.
- Key Point: Anyone already running the earlier GitHub notifications app keeps existing alert features as long as the installation is updated to the current release.
How a complaint becomes a pull request
Notifications reach Teams through channels, group chats and one-to-one conversations, and the mention of @GitHub is what converts an update into action. From there the assistant investigates the underlying issue, writes the fix and raises the pull request, at which point the ordinary checks resume: teammates read the diff, run tests and decide whether to merge.
Users mention @GitHub and follow the prompts to link a GitHub account and choose a repository, which is the point where the assistant learns what it is allowed to touch.
A retirement date for the old integration
The consolidated app replaces two earlier setups. People who already have GitHub notifications installed only need to update to the newest version, and their notification features will keep working as before. Those still on the legacy GitHub app face a harder deadline: that software is being relabeled “GitHub (deprecated)” and will be switched off on November 16, and Copilot inside Teams will not be reachable through it after that point.
Uploading the consolidated app is the migration path, and the account-linking prompts carry over. For administrators, the practical question is scope: because the assistant acts on a repository after a mention, it matters which connected accounts and which projects are exposed inside a workspace where large numbers of colleagues can post.
Why the chat window keeps absorbing developer work
The GitHub integration is one example of a larger shift in how collaboration software is being positioned. Microsoft’s own guidance for development teams argues that the hidden expense of modern engineering is context switching, and that AI earns its place when it absorbs the mental cost of moving between writing code, writing tests, updating documentation and reviewing someone else’s pull request. The same material describes automated test generation, tools that generate README and onboarding documentation, and review assistants that flag vulnerability patterns and style drift so human reviewers can concentrate on design.
Third-party connectors have already been pushing tracker data the other way, creating a shared Teams chat for each epic, posting sprint and release updates into channels and returning AI-written summaries of those conversations to the project backlog. Microsoft’s adoption material for Copilot takes a similar line, recommending short activation sprints built around a single everyday task, with better meeting follow-up as a common starting point: summarizing decisions and open questions, then drafting the message that goes out afterwards.
What comes next hangs on the November 16 cutoff. Organizations that leave the deprecated app in place will lose the Copilot route into their repositories, and the decision about who may summon an assistant that writes code from a chat message will land on IT and security teams rather than on the developers who requested the feature. Microsoft has promised more Teams capabilities for this audience, but the rollout pattern it has described suggests the pieces will arrive unevenly, with some tenants waiting longer than others.