@GitHub in Slack and Teams Is Generally Available, With Canvas in Teams
GitHub announced that @GitHub in Slack and Teams is generally available, and added Canvas in Teams so users can review implementation plans, code changes and previews alongside their conversation. @GitHub now identifies the repository from the message, and issues and pull requests it creates are attributed to the originating Slack or Teams conversation.
Key Takeaways
@GitHubin Slack and Teams is generally available, per the announcement title.- Canvas in Teams lets users review implementation plans, code changes and previews alongside the conversation.
@GitHubidentifies the repository from the message, removing a repeated repository-selection step.- Issues and pull requests carry "Created from a Slack/Teams conversation with @username" in their description.
- GitHub says setup is easier when a user is signed out, has no default repository, wants to switch repositories, or needs app access.
- A fix addressed an issue that could prevent responses to follow-up messages.
Generally Available
GitHub announced that @GitHub in Slack and Teams is generally available. From either chat app, users can investigate bugs, create issues, implement changes and open pull requests without switching tools.
Build and Review Together With Canvas in Teams
With Canvas, users can review implementation plans, code changes and previews alongside their conversation, and refine the work with teammates without leaving the chat.
Faster Onboarding
@GitHub now identifies the repository from the message, so users no longer need to select it again before the session launches. GitHub describes the goal as going from request to coding session in fewer steps, and says setup is easier when a user is signed out, lacks a default repository, wants to switch repositories, or needs app access.
Clearer Attribution and a Reliability Fix
Issues and pull requests created by @GitHub now include "Created from a Slack/Teams conversation with @username" in their description, which ties the work back to the discussion that prompted it.
GitHub also fixed an issue that could prevent responses to follow-up messages.