GitHub in Slack and Teams: Multi-repository support, improved conversation context

1. Conversations continue across repositories

GitHub announced multi-repository support in its October 15, 2026 changelog. A repository stores a project's code and change history. This update lets users request work across separate repositories in one conversation.

For example, users can request a bug investigation covering both frontend and server code, even if they are in separate repositories. The key is that conversations are no longer tied to one repository, not that repositories are merged.

2. From creating issues to reviewing pull requests

The source gives four use cases. The first is requesting an issue in a specific repository to track a bug discussed in a conversation, using that conversation's context. This turns a discussion into a work item.

The second is fixing a bug in a frontend repository and opening a pull request. A pull request proposes code changes for review before inclusion in a project. Here, one request connects code editing with creating a review request.

The third is gathering your open pull requests across repositories and identifying those needing attention. The fourth is investigating an issue using both frontend and server code. These cover scattered work and cross-repository problems.

3. Mention placement and Slack context use also change

GitHub mentions are now more flexible. Users can mention @GitHub anywhere in a message, not just at the beginning. The source also describes improvements that make switching repositories during a conversation easier.

In Slack, shared messages and conversation threads can provide context for tasks. This reduces the need to copy and paste details to explain earlier discussions. The source does not say whether Teams offers the same context feature.

4. Task startup and recovery after interruptions improve

GitHub says it has reduced errors, improved task startup, and made recovery after interruptions smoother in both messaging platforms. These reliability improvements were announced alongside multi-repository support.

This does not guarantee uninterrupted task completion. No figures were provided for error reduction, startup time, or recovery success rates. The direction is clear, but there is no numerical basis for comparing speed or stability gains.

5. Weigh switching effort against review scope

The benefit is less effort moving between conversations for different repositories. Investigations spanning multiple repositories can keep related requests in one flow. Slack context use also reduces the need to repeat earlier discussions.

However, the convenience of handling multiple repositories should be distinguished from the scope of reviewing results. Teams should weigh fewer conversation switches against the effort of checking which repository each request and result concerns.

The source does not specify the maximum repositories per conversation, exact steps for switching repositories, or plan and billing coverage. These conditions need separate confirmation when considering adoption.

This update connects work across repositories in one conversation, and adoption decisions should weigh the convenience of switching against the effort of reviewing the scope of work.