GitHub in Slack and Teams Adds Multi-Repository Work in One Conversation
A cross-repository update, not an initial integration launch
Key takeaways
GitHub’s Slack and Teams integration can now work across multiple repositories within a single conversation. That is useful when a reported problem spans a frontend and backend, but it is a different event from the original launch of the chat integrations. This article explains the change and provides a scoped investigation request that a non-programmer project owner can give a technical collaborator. It describes what evidence to request before moving from analysis to code changes and how to distinguish an issue, a proposed pull request, a merge, and a deployment. No account-level availability test or automatic resolution is claimed, and the announcement is not treated as permission to change every repository.
By ENHE AI · 2026-10-19 · AI-assisted drafting and editorial checks.
Direct answer: keep cross-repository context in one conversation
The October 15 update lets @GitHub in Slack and Teams work across multiple repositories in one conversation. For a page error that may originate in an API, the practical benefit is keeping related clues together instead of splitting them into disconnected conversations.
Existing coverage of the original integrations remains relevant; this article focuses on the cross-repository update. The example below is a suggested request, not a recording of a successful action in a team workspace.
What is confirmed, and what is not
GitHub announced the update on October 15, 2026. Examples cover creating issues, opening pull requests, tracking open PRs across repositories, and investigating frontend and backend code together. The update also permits mentioning @GitHub anywhere in a message and using shared Slack messages and threads as context.
The announcement does not provide a full account-and-pricing matrix or guarantee automatic fixes, merges, or deployments. Check access to private repositories within the actual installation and permissions; multi-repository support does not mean access to every repository.
Example: investigate a frontend/backend problem first
- Record the page, action, expected and actual behavior, a shareable error message, and the time observed. Remove access tokens, personal information, and client content.
- Example input: “@GitHub Investigate filter pagination mismatches in organization/site-web and organization/site-api, read-only. List relevant files and evidence first. Do not edit, create a PR, or deploy.” Replace the names with repositories you are authorized to access.
- Check whether the response distinguishes evidence from each repository, confirmed facts, and hypotheses. Repeating the chat does not establish a code-level cause. Missing access to a repository should be stated explicitly.
- For a later change, specify allowed files, tests, and delivery separately. An issue records work, a PR proposes changes, and merge and deployment are additional states. Do not label all of them “live.”
What this means for a non-programmer project owner
You do not need to decide in advance whether the bug is frontend or backend. Supply the problem and two exact repositories together, then ask what was inspected, what was found, and what remains uncertain. Otherwise the change merely produces a longer conversation.
The existing Slack preview, Teams preview, and collaboration-approval checklist provide background and permission guidance. Their earlier preview dates are not the date of this cross-repository update.
FAQ
Is this the original Slack launch republished?
No. The distinct event here is multiple repositories within one conversation. Initial-preview coverage remains linked as background.
Will naming two repositories automatically change code?
Do not assume that. Specify read-only analysis or the permitted change scope, then inspect the actual activity record.
Related tools and reading
Use the following relevant pages for account context, reusable instructions, or the earlier events discussed above.
- Slack integration preview background
- Teams integration preview background
- AI collaboration-approval checklist
Conclusion
Start with a clearly scoped investigation and evidence from both repositories before authorizing a change.
What this means for everyday users
You do not need to decide in advance whether the bug is frontend or backend. Supply the problem and two exact repositories together, then ask what was inspected, what was found, and what remains uncertain. Otherwise the change merely produces a longer conversation.
Related tutorials
Related reading
GitHub Copilot Enters Slack Public Preview for Shared Coding Work
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Copilot Enters Slack Public Preview for Shared Coding Work.
GitHub Copilot Brings Shared Agentic Work to Microsoft Teams
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Copilot Brings Shared Agentic Work to Microsoft Teams.
How to Adopt AI Agents in Slack and Teams with an Approval Checklist
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for How to Adopt AI Agents in Slack and Teams with an Approval Checklist.
From Chat Boxes to Personal AI Companions: AI Assistants Are Entering the Desktop Execution Era
AI assistants are moving from answering questions toward continuing real tasks. AI agents, MCP tool ecosystems, personal memory, and local workbenches are pushing this shift together. For users, the real value is not another chat box, but less repeated context setup and more continuity from thinking to doing.
Eleven Realtime v1 Mini and Max Launch: Choosing a Voice-Agent Path
ElevenLabs launched Eleven Realtime v1 Mini and v1 Max on October 20, 2026. Both speech-to-speech models support more than 90 languages and over 17,000 voices, but they target different tasks: Mini emphasizes lower-cost natural conversations, while Max is designed for support, lead qualification, and multi-step work. This article offers a selection and migration checklist instead of repeating benchmark claims. It explains how to compare both models on the same script, what OpenAI Realtime API compatibility means, why WebRTC integrations must move to WebSocket, and when ElevenAgents is the better starting point for channels, knowledge bases, guardrails, testing, and monitoring.
GitHub CLI Adds Expiring OAuth Tokens: Check Git, Scripts, and Extensions First
GitHub announced an opt-in public preview of expiring, automatically refreshing OAuth credentials for GitHub CLI on October 21, 2026, beginning with version 2.103.0. Users can enable the behavior with gh auth login --expiring or a global configuration setting. Git over HTTPS should use gh auth setup-git, and Git 2.46 or newer is recommended to avoid caching credentials beyond their lifetime. This article focuses on AI coding tools, scripts, and extensions that capture gh auth token output once and reuse it. It provides an inventory, migration, and verification sequence so users can gain a shorter exposure window without unexpectedly breaking long-running automation.