One conversation, several repositories
GitHub announced on October 15 that Copilot in Slack and Teams can work across multiple repositories in a single conversation. The update also improves repository switching and lets the Slack integration use shared messages and threads as context.
That is the announced scope, not a claim that the integration can access every repository or conversation in your organization. Check your installed integration and access configuration before assuming a particular source is included.
Source: GitHub: Multi-repo support and other improvements for GitHub in Slack and Teams ↗
Ask for a comparison you can inspect
Our suggested first use is a small question about two repositories you already understand. Name them explicitly, define a time window, and ask the assistant to separate what it found in each. A blended paragraph may read smoothly while making it hard to see which project supplied the evidence.
Imagine a student team with an app repository and a documentation repository. Instead of asking whether everything is ready, ask what changed in each during the same period and which open questions connect them. Then inspect the underlying items before making a release decision.
Treat a chat discussion as context for investigation, rather than proof that an implementation is complete. If the assistant reports that something shipped, ask what artifact or merged change supports that statement. If the evidence is missing, the useful answer may be a question to resolve rather than a status label.
Keep the experiment small
Choose a past week whose activity you know. Compare the assistant’s summary with the repository records, noting missing items, misplaced items, and claims that need a source. You do not need to connect additional projects to learn whether the summary format helps.
Before widening the scope, decide which channels and repositories belong in the workflow. Do not paste private material into a broader conversation just to make a demo work. A good cross-repository answer should make its sources easier to navigate, not make access boundaries harder to understand.
Try this, then make it yours.
Ask for a separate activity summary for two authorized repositories over one completed week and check the cited records.
Explore the tool ↗Follow the signal.
Our reporting starts here. Practical suggestions are our analysis, and vendor performance statements are claims unless independently verified. We haven’t hands-on tested this release.
