Multi-repo support and other improvements for GitHub Copilot in Slack and Microsoft Teams

[sunnyi101]

Multi-repo support in Slack and Microsoft Teams

multireposupport.mp4

GitHub Copilot in Slack and Microsoft Teams now supports working across multiple repositories in a single conversation. Whether you’re tracking pull requests, investigating issues, or catching up on project activity, you can get the information you need across repositories without switching between conversations.

For example, you can ask Copilot to:

• Track your work: “@github Show me all my open pull requests across repositories and highlight which ones need my attention.”
• Get updates: “@github What pull requests were merged this week across my repositories?”
• Investigate issues: “@github Help me investigate an issue that spans our frontend and backend repositories.”
• Review progress: “@github Summarize recent activity across our repositories.”

You can ask these questions directly in Slack or Microsoft Teams, making it easier to stay on top of work across projects without leaving the conversation.

Additional improvements

We’ve also made several improvements to GitHub Copilot 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: Copilot 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 Copilot recover more smoothly from interruptions in Slack and Microsoft Teams.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[AconiteX]

would love to also see these integrations available with Discord for those of us whose open source projects don't use something as formal as Slack