@GitHub in Slack and Teams now supports working across multiple repositories in a single conversation. Whether you’re creating issues, opening pull requests, or investigating bugs, you can work across repositories without switching conversations.

For example, you can ask @GitHub to:

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.”

You can do all of this directly from Slack or Teams, without switching repositories or starting a new conversation.

Additional improvements

We’ve also made several improvements to GitHub in Slack and Microsoft Teams:

More natural conversations: Mention @GitHub anywhere in your message, not just at the beginning.
Smoother repository switching: Move between repositories more easily during a conversation.
Better Slack conversation context: @GitHub can use shared Slack messages and threads as context, making it easier to reference discussions without copying and pasting details.
Improved reliability: We’ve made several improvements to reduce errors, improve task startup, and help @GitHub recover more smoothly from interruptions in Slack and Teams.

Join the discussion within the GitHub Community.