What changed
GitHub’s October 23 update brings repository notifications and Copilot into one Teams app. Teams can move from a bug notification to an agent task and a proposed pull request in the conversation. People still need to inspect the code, run relevant tests, and decide whether to merge.
The migration depends on which app is installed. Teams using GitHub notifications should update that app; GitHub says existing notification features continue. Teams using the legacy GitHub app need the consolidated replacement. That older app will be renamed GitHub (deprecated) and retired November 16. Users then mention @GitHub, connect their GitHub account, and select a repository.
Check access and conversation context
Copilot cloud agent remains a public preview for paid Copilot plans. Cloud sandboxes must be enabled, and organization or enterprise policies may require an owner’s action. GitHub’s general Teams setup guide also lists Microsoft Public Developer Preview for the Teams client. Check the current instructions before assuming every colleague has access.
GitHub documents that the full thread becomes task context and is stored in generated artifacts. A direct message can narrow that context. Direct messages use the linked personal account’s permissions; shared conversations create artifacts under the app identity. Repository write access is required to trigger changes, while other participants can contribute input.
Our take
For a small development team, the migration deadline is a useful reason to check app identity, repository access, and notification settings together. Start with a focused thread and a bounded task. A shorter handoff can reduce ambiguity. Keep code review and appropriate tests attached to the pull request before a person decides whether it is ready.
We have not installed or tested the integration. The announcement is dated October 23; its exact posting hour was not established.