GitHub Copilot now connects multiple repositories in a single conversation in Slack and Microsoft Teams
GitHub Copilot in Slack and Microsoft Teams now lets users track changes and investigate issues across multiple repositories in a single conversation. In Slack, it can also use shared messages and threads as context.
GitHub has enabled users of GitHub Copilot for Slack and Microsoft Teams to work with multiple repositories in a single conversation. Users can request an overview of open pull requests, find out which were merged during the week, or get a summary of recent activity across repositories. Support also includes investigating issues that affect multiple repositories, such as separate client and server components of a project.
The @GitHub mention can now be placed anywhere in a message. In Slack, GitHub Copilot can use shared messages and threads as context. According to GitHub, this makes it easier to build on previous discussions without copying their content.
Why it matters
When working on a project split across multiple repositories, users can combine an overview of changes with an investigation of related issues in a single conversation. In Slack, this investigation can also draw on the context of the team discussion.
Two audiences, two different impacts
What this means
For individuals
A developer can use a single query to get an overview of their open pull requests across repositories and ask for those requiring attention to be flagged.
For a business
Development teams can work together to investigate connections between the repositories for the client and server components of a project directly in their work conversation.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.