// AI Platform Drift

GitHub Copilot in Slack/Teams adds issue creation and PR opening

GitHub Copilot changelog · published 2026-10-17 04:30 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDGitHub Copilot's Slack and Teams integration now creates issues and opens pull requests directly from chat. The bot was renamed from 'GitHub Copilot' to '@GitHub'. New capabilities include '@GitHub Create an issue in github/issues to track this bug' and '@GitHub Fix this bug in our frontend repository and open a PR with the changes.' Previous examples focused on read-only operations like tracking PRs and summarizing activity.
WHY IT MATTERSThe integration now writes to repositories, not just reads from them. Any team using this bot in Slack or Teams needs to verify that its repository permissions align with the new write capabilities, particularly for issue creation and PR opening. The rename from 'GitHub Copilot' to '@GitHub' may break existing slash commands or automation that references the old name.
WHAT TO DOCheck the bot's installed permissions in your GitHub organization settings and confirm they match your policy for automated issue creation and PR opening. Update any documentation, runbooks, or scripts that reference 'GitHub Copilot' in Slack/Teams to use '@GitHub' instead.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://github.blog/changelog/2026-10-15-copilot-in-slack-and-teams-adds-model-and-repository-updates
 Fri, 16 Oct 2026 02:16:35 +0000
 
-GitHub Copilot in Slack and 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.
+@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:
-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.
+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 Copilot in Slack and Microsoft Teams:
+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.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.72, needed 0.5
triage reasoningNew code-modification and issue-creation capabilities represent functional expansion of the Slack/Teams integration.
signalsnew capability: create issues from conversations · new capability: make code changes and open PRs · branding change: 'GitHub Copilot' → '@GitHub' · example use cases replaced with new, broader actions · capability expansion: direct code modification and PR creation
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)