How to Integrate GitHub With Slack in 5 Minutes (And What to Do Next)

By Fahad Ijaz · · 5 min read

The basic GitHub + Slack setup takes about five minutes. The harder problem is what to do once the notifications are flowing and your team starts asking you to turn them off.

Step 1: Install the GitHub App in Slack

In any Slack channel, type /github subscribe owner/repo. Slack will prompt you to authenticate with GitHub and confirm permissions. If you don't have admin access to the GitHub organisation, an org owner will need to approve the install. This is a one-time setup per workspace.

Step 2: Choose What to Subscribe To

By default the integration subscribes you to PRs, issues, commits to the default branch, releases, and deployments. You can pare this down with /github subscribe owner/repo pulls,issues,releases. For a busy repo, picking three event types instead of seven is the difference between a usable channel and one everyone mutes.

Step 3: Pick the Right Channel Strategy

Two patterns work. Per-repo channels (#repo-frontend, #repo-api) keep noise contained but require people to remember which channel maps to which service. Per-team channels (#team-checkout, #team-growth) align with how people actually think about work but mix events from multiple repos. The team-channel approach scales better past five repositories.

Step 4: Add a Plain-English Layer for Non-Engineers

Once the technical channels are humming, the next request is always 'can we get something like this for the product team?'. The native integration won't help here, the events are too low-level. This is where Figorit's Slack bot slots in: install it once, and anyone in any channel can ask plain-English questions about the same repos. Same source of truth, different output.

Common Setup Mistakes

Subscribing to every event type on day one (you'll mute the channel within a week). Putting all repos into one channel (it becomes unreadable past three). Forgetting to subscribe to the main branch only for commits (every feature-branch push will spam the channel). And not setting up a separate channel for security alerts, which deserve attention that gets lost in PR noise.