GitHub in Slack and Teams now works across repos in one conversation

GitHub’s October 15, 2026 update lets people already using its Slack and Microsoft Teams integrations work across multiple repositories without starting a new conversation.

Investigate frontend and backend together

A bug investigation can draw on more than one repository within the same discussion. GitHub illustrates this with a request asking @GitHub to investigate an issue using code from both frontend and backend repositories.

Turn a discussion into an issue or a proposed fix

Other official examples include creating an issue in a named repository using the thread’s context, or fixing a bug in a frontend repository and opening a pull request (PR)—a proposed code change submitted for review.

For work already underway, another example asks @GitHub to list the user’s open PRs across repositories and highlight those needing attention.

More flexible mentions, less copying in Slack

You can now mention @GitHub anywhere in a message, rather than only at the beginning. In Slack specifically, shared messages and threads can supply context without copying and pasting the discussion’s details.

The update also includes smoother repository switching and reliability improvements aimed at reducing errors, improving task startup and helping @GitHub recover from interruptions in Slack and Teams.