To connect GitHub to Slack, install the GitHub integration for Slack, sign in with /github signin, then run /github subscribe owner/repo in a channel to get issue, pull request and push notifications. The connector route is Zapier, which can post a Slack channel message when a new pull request or issue appears.
A busy repository and a quiet Slack channel don't mix well. Developers miss reviews, product people miss releases, and everyone ends up refreshing GitHub. Piping the right events into the right channel fixes that, as long as you choose what to send.
Native app or Zapier
| GitHub integration for Slack | Zapier | |
|---|---|---|
| How it works | Slash commands in a channel | A trigger and an action you build |
| Events | Issues, pull requests, commits, releases, deployments and more | Triggers such as New Pull Request and New Issue |
| Speed | Posts as events happen | Polls GitHub on a timer |
| Best for | Development teams | One simple alert, or a custom message |
The native app officially supports GitHub.com, including GitHub Enterprise Cloud, with Slack.com. GitHub Enterprise Server works with Slack.com from GHES 3.8. Its code isn't open-source, but it's GitHub's own integration.
Getting the GitHub app running
- Install the GitHub integration for Slack and approve its access in your Slack workspace.
- Connect your GitHub account by following the prompt, or run /github signin.
- If the channel is private, run /invite @github in it. The app is enabled in all public channels automatically.
- Run /github subscribe owner/repo in the channel. You can subscribe to a whole organisation the same way.
- Add more event types with /github subscribe owner/repo reviews comments, or remove them with /github unsubscribe.
- Narrow things down with a branch filter or a label filter if the channel gets noisy.
What you'll see by default, and what you won't
Out of the box, the app posts open, close and re-open events on pull requests and issues, plus pushes to the default branch. In feature terms, issues, pulls, commits on the default branch, releases and deployments are on.
The integrations/slack README on GitHub is clear about the rest: workflows, reviews, comments, branches, discussions and commits on every branch are off by default. That surprises teams who expect code review requests to appear the moment they connect. You switch each one on per repository with /github subscribe, so if reviews matter to your team, add them on day one.
Branch and label filters
Branch filters look like /github subscribe org/repo commits:myBranch. Use commits:* to cover every branch. The older commits:all is no longer a reserved keyword, so don't rely on it.
Label filters such as +label:"priority:HIGH" work for pulls, issues, comments and reviews. They don't apply to commits or branches. A neat setup is a dedicated urgent channel subscribed only to items with a high-priority label, so the people on call see what matters and nothing else.
Keeping each channel useful
The commands work per channel, so you can shape each one to its audience. A developers channel might carry pulls, reviews and comments for one repository. A product channel might only want releases and deployments. If a channel starts drowning in alerts, /github unsubscribe owner/repo followed by the feature names switches those events off again without touching anything else. Small changes like this are what keep people reading the channel instead of muting it.
The access the app asks for
The app needs read access to code and several repository objects so it can render link previews in Slack. It needs write access to actions, issues, deployments and pull requests so you can act on them from Slack. If your security team asks why, that's the reason.
The Zapier route
Zapier's GitHub and Slack page lists triggers such as New Pull Request and New Issue, which poll GitHub on a timer, paired with Slack's Send Channel Message action. That action needs a Channel and Message Text. On Zapier's Free plan the page notes a 15 minute polling interval as of Nov 2026, so expect a delay. It's fine for a weekly digest channel, less so for anything urgent.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Not on GitHub?
GitLab offers its own native GitLab for Slack app, with slash commands and notifications. If you're weighing up a move, my roundup of GitHub alternatives covers the options.
My advice for a small development team
Use the native app, give each repository its own channel, and switch on reviews and comments straight away rather than wondering why nobody sees review requests. Add a label filter for urgent work. Keep Zapier for the odd custom alert outside the team. And if Slack itself feels too noisy for your team, my list of Slack alternatives is worth a read.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Is the GitHub Slack app official?
Yes. It's the GitHub integration for Slack, built by GitHub.
How do I get notifications in a private channel?
Run /invite @github in the channel, then /github subscribe owner/repo.
Can I get commit notifications for every branch?
Yes, with /github subscribe org/repo commits:*.
Can I filter by label?
Yes, for issues, pull requests, comments and reviews, using +label:"name".
Is there a no-code alternative?
Zapier can post a Slack channel message from GitHub triggers.