GitHub announced on November 6, 2026 that @GitHub in Slack and Microsoft Teams is generally available. A participant can mention the assistant in a conversation to investigate a bug, create an issue, ask for a code change and move toward a pull request. The release matters because an app request often begins as a message from a teammate or user, long before it becomes a tracked development task. GitHub's announcement describes a workflow its own assistant can perform; VIBPS has not tested the integrations.
What happens after you mention @GitHub?
In Slack, GitHub describes a shared Copilot session that keeps the task plan, branch and eventual pull request connected to the original discussion. More complex work can move into a Code Channel, where participants can add context and follow progress. In Teams, the same mention can start a shared session in a channel, group chat or meeting chat. Teams Canvas shows the plan, changed files and pull request beside the conversation. GitHub says the assistant can identify a repository from a message when possible, reducing a setup step, but the correct repository and requested change still need human review.
A conversation is useful context, not a complete specification. If a report says an app is broken, someone still needs to identify the affected route, expected behavior and evidence that the proposed fix works. GitHub's Slack page says the assistant can turn a discussion into an issue with reproduction steps and acceptance criteria. That is a useful bridge between a report and code, but the generated issue and pull request should be checked against the actual product.
Can anyone in the chat authorize a code change?
No. GitHub's product FAQs distinguish contributing context from authorization. Repository permissions and existing approval rules determine who can authorize and merge changes. The November release also adds attribution in issues and pull requests created through the assistant, identifying that they came from a Slack or Teams conversation. A maker reviewing a change can therefore see where the request began, then inspect the diff, checks and approvals on GitHub. The integration does not make a chat message equivalent to a merge approval.
What does setup require?
GitHub offers separate Add to Slack and Add to Microsoft Teams entry points. The Slack workspace may require an administrator to approve the app and its requested permissions. GitHub's Teams FAQ lists Microsoft 365 app-policy and resource-specific consent requirements, plus GitHub enterprise controls for Copilot cloud agents and licenses. Teams may use the whole mentioned thread as context. Before enabling the integration in a workspace, administrators and makers should understand which conversations and repositories it can access. GitHub does not present this as a permission-free path from any chat into a private codebase.
Where does this fit in an app's journey?
For teams that already coordinate in Slack or Teams, the new general availability can shorten the handoff from a product discussion to a reviewable code change. That is an inference about workflow, not a measured time saving. The pull request still needs review and the resulting app still needs to work for its audience. VIBPS is the social network for software, where makers can present what they built and connect an app with people who want to follow it. GitHub's assistant serves the earlier development stage; it is GitHub's product, not a VIBPS feature.