Multi-repository support and other improvements for GitHub in Slack and Teams
By Steven Van ·
GitHub's Slack and Teams agent can now create issues, open PRs and investigate bugs across several repositories without leaving the conversation.
Multi-repository support has arrived in GitHub for Slack and Microsoft Teams. A single conversation with @GitHub can now span several repositories, so there is no need to switch conversations or start a new one for each repo. The change was announced in the GitHub changelog.
What you can ask across repositories
GitHub's examples cover four kinds of task:
- Create issues from conversations: "@GitHub Create an issue in github/issues to track this bug, using the context from this thread."
- Make code changes: "@GitHub Fix this bug in our frontend repository and open a PR with the changes."
- Track your PRs: "@GitHub Show me all my open PRs across repositories and highlight which ones need my attention."
- Investigate bugs: "@GitHub Investigate this issue using the code in our frontend and backend repositories."
Other improvements
- More natural conversations: @GitHub can be mentioned anywhere in a message, not only at the beginning.
- Smoother repository switching: moving between repositories during a conversation is easier.
- Better Slack conversation context: @GitHub can use shared Slack messages and threads as context, so discussions can be referenced without copying and pasting details.
- Improved reliability: GitHub made changes to reduce errors, improve task startup, and help @GitHub recover from interruptions in Slack and Teams.
GitHub
Where the world builds software — Git hosting, pull requests, issues, Actions CI/CD, and Copilot, free for public and private repos.
View GitHub →