CodeStream is a developer collaboration platform that integrates all of your essential dev tools, such as GitHub, GitLab, Bitbucket, Slack, Teams, Jira, Trello and more, into VS Code, Visual Studio.
If you are using Slack(Yes it’s awesome) and Github Enterprise(Awesome too), then you might have played around with the integration of both the tools.
The Slack documentation helps a bit but to have a complete integration with issues
, issues comments
etc, you’ll have to jump through some hoops. So let me put it all below.
First step is to obviously add a hook in your company’s Github Enterprise repo for Slack. Skip to next section if you’ve already addded the Github Webhook.
Click on the Add Service Integration menu link for your group
Select your Slack group or channel where you want the Github notifications:
Now click on the switch to unauthed mode
Copy the Webhook URL you see on the next screen. Now goto the Settings > Hooks page of your repo in Github Enterprise. Add a Webhook and paste the Webhook URL there.
After adding the Webhook you should receive notifications when anyone pushes commits to your repo.
Now you may have noticed that even after adding a Webhook, you can only see notifications for new commits
. The integration is still missing notifications for events such a new issue
or issue comment
etc.
The reason is that Webhook only publishes commit events by default. You can change this behaviour by altering the hook via Github Webhook API
Assuming your Github Enterprise link as http://githuben.mycompany.com/
, your organization as myorg
and repo as myrepo
1 . Find your hook url (containing the hook id) by retrieving a list all the hooks
for a repo
:
You should see a big JSON
output. All you need is the url
of the hook matching your Slack Webhook integration url.
You can see in the JSON
aboce, that events
in the hook is only push
. The url for our Slack hook is - http://githuben.mycompany.com/api/v3/repos/myorg/myrepo/hooks/1121
2 . Now add all the extra notifications to the events
for the Webhook using the hook url
from above:
That’s all. You should now be able to receive notifications for all these events apart from push. You can call the Get Hooks
api again to confirm.
Bring your code to the conversations you care about with the GitHub and Slack app. A separate Slack subscription is required. With two of your most important workspaces connected, you’ll get updates about what’s happening on GitHub—without leaving Slack.
Subscribe to repositories
Use /github subscribe [owner/repo]
in Slack to start receiving updates about that project.
Stay up to date
Get updates about what’s happening with your repositories in Slack discussions for activities like:
See the details
Give your team more information in Slack when you share links to GitHub activities and properties like:
Take actions with slash commands
Slack conversations often lead to decisions and actionable takeaways. Now it’s easier to start on next steps from Slack with slash commands for common GitHub actions, using /github [action] [resource]
. For example, these commands let you:
Your ultimate productivity pair
Slack + GitHub is owned and operated by GitHub with separate terms of service, privacy policy, and support documentation.