// the find
integrations/slack
Bring your code to the conversations you care about with GitHub's integration for Slack
This is GitHub's official Slack integration — a closed-source app that sends GitHub notifications (issues, PRs, commits, deployments, Actions runs) to Slack channels. The repo exists mainly as a documentation and issue tracker stub; the actual running code lives in GitHub's private infrastructure and hasn't matched what's here for years. Useful to anyone wanting to understand the subscription command syntax or file a bug.
The subscription model is genuinely flexible: per-feature toggles (reviews, comments, branches, discussions), branch-pattern filters for commits, and label allowlists for issues/PRs give teams real control over noise. Threading notifications under a parent card is a smart UX choice that keeps channels readable without hiding context. The mentions mapping (GitHub user → Slack user) for PR reviewers and issue assignees is well thought out — it surfaces the right pings without spamming the whole channel. GHES support via a self-generated private app is a practical option for on-prem shops that need the same feature set.
The repo itself is a shell — the README says outright 'the code is not open-source and is not available here' and contributions are explicitly rejected. You cannot self-host this, audit what it's doing with your code read permissions, or patch anything. The permission scope asks for read access to code, which is a meaningful trust decision most teams accept without thinking about it. The GHES setup flow is a 14-step manual process involving Slack API configuration tokens and socket mode wiring — it's functional but clearly not productized to the same level as the cloud version. Threading cannot be opted out of cleanly; the workaround documented for avoiding thread pings is to log into GitHub from a throwaway Slack workspace, which is a hack, not a feature.