GitHub Notifications in Discord: 3 Working Methods
A lot of teams already live in Discord and want GitHub activity delivered there instead of juggling another inbox. There are three real ways to do it. Here's each one, set up in plain steps — plus an honest note on where each falls short.
Method 1: The official Discord webhook (built into GitHub)
This is the standard approach and requires no third-party service:
- In your Discord server, open Server Settings → Integrations → Webhooks and click New Webhook. Choose the channel it should post to and copy the URL.
- In GitHub, go to repo → Settings → Webhooks → Add webhook.
Paste the Discord URL and append
/githubat the end — that suffix switches Discord into GitHub payload mode. - Set Content type to application/json. Under Which events?, pick only what you need — defaulting to Send me everything is the single biggest source of webhook spam.
- Add it and use the Recent Deliveries tab plus Redeliver to test without waiting for a real push.
Where it falls short: webhooks are repo-level and event-level, not people-level. You'll get pushes for every branch and every issue — but you won't reliably get notified about reviews that need you personally. Teams typically mute the channel within a week.
Method 2: A Discord bot (per-user routing)
Bots like Github-Discord bridges or Coderbot-style integrations can map individual GitHub users to Discord users, so a review request pings you rather than a channel. Setup usually means inviting the bot via OAuth, connecting your GitHub account, and subscribing to the events you care about.
Where it falls short: you're trusting a third-party service with your repository webhooks — and if the bot's hosting dies, so does your notification pipeline. Check whether it's actively maintained before wiring your team to it.
Method 3: Skip Discord entirely — a local menu bar app
If your actual problem is "I miss review requests" rather than "I want more channels," moving notifications into yet another chat app adds noise instead of removing it. A local option like DevNotify polls GitHub directly and puts unread PRs, issues and mentions as a badge in your macOS menu bar — no channel to mute, no third-party bot holding your webhooks, nothing leaves your machine.
Which should you pick?
| Webhook | Bot | Menu bar app | |
|---|---|---|---|
| Best for | Team-wide repo activity in one channel | Per-person pings inside Discord | Your own review requests & mentions |
| Setup time | ~5 min | ~15 min + OAuth trust | ~2 min |
| Noise level | High — mutes itself quickly | Medium | You control what counts as unread |
| Data leaves your devices? | Yes (to Discord) | Yes (to the bot host) | No |
| Fails when… | Event filters misconfigured | Bot goes unmaintained | — (polls GitHub API directly) |
The combination that actually works
Many developers end up running two layers: a narrowly-filtered webhook for deploys and releases (things the whole team should see), and a personal layer for anything addressed to them individually. If your personal layer lives in the same window as team chatter, it gets lost — which is exactly why the menu bar approach works better for it.