How to connect GitHub to Discord
There are two ways. Discord's built-in GitHub webhook posts a repository's events into one channel. A GitHub App bot such as ForgeFeed routes each kind of event to its own channel and keeps boards and workflow runs up to date in place.
Updated · By Digital Den
Use Discord's built-in GitHub webhook
No bot, no account, and free. Best for one repository whose events can all share a channel.
GitHub · Settings · Webhooks
- Payload URL
- https://discord.com/api/webhooks/1234/abcd/github
- Content type
- application/json
- Which events would you like to trigger this webhook?
- ○ Just the push event · ○ Send me everything · ● Let me select individual events
- 01
Create a webhook in Discord
Open the channel's settings with Edit Channel, go to Integrations, then Webhooks, and create a new webhook. Give it a name, then press Copy Webhook URL. You need the Manage Webhooks permission on that channel.
- 02
Add /github to the end of the URL
Discord formats GitHub's payloads only on its GitHub-compatible endpoint, which is the same URL with /github on the end. Without it, nothing readable is posted.
- 03
Add the webhook to the repository on GitHub
In the repository, open Settings, then Webhooks, then Add webhook. Paste the URL as the Payload URL and set Content type to application/json.
- 04
Choose the events, then save
Pick Just the push event, Send me everything, or Let me select individual events, keep Active ticked, and press Add webhook. Repeat for every repository, or, as an organization owner, add one webhook from the organization's own settings to cover all of its repositories.
Events Discord understands
Discord's GitHub endpoint accepts these 18 event types and ignores the rest. watch is GitHub's name for stars.
- push
- pull_request
- pull_request_review
- pull_request_review_comment
- issues
- issue_comment
- commit_comment
- create
- delete
- fork
- watch
- release
- check_run
- check_suite
- discussion
- discussion_comment
- member
- public
Limits to know
- Each webhook posts into one channel. Sending pull requests and releases to different channels means a webhook per channel, per repository, each with its own events.
- Every event is a new message. Nothing is edited in place, so an active repository fills the channel quickly.
- GitHub Actions results arrive as check_run and check_suite events. The workflow_run event is not one Discord's endpoint accepts.
- GitHub does not redeliver failed deliveries on its own. Missed events stay missed unless someone redelivers them from the webhook's Recent Deliveries tab.
Use a GitHub bot for Discord: ForgeFeed
ForgeFeed reads GitHub as a GitHub App, so there is no webhook URL to paste anywhere. Each kind of event goes to the channel you pick, and boards stay current in place.
- 01
Add ForgeFeed to your server
Use the invite link. ForgeFeed DMs whoever added it with a pointer to /setup, and posts a welcome with a Connect a repo button in the server.
- 02
Run /setup and link GitHub
Press Install GitHub App, or Already installed if it is on the account already. GitHub sends you to a ForgeFeed page that names the server. Press Link there, and the message in Discord moves on by itself. No webhook URL and no personal access token.
- 03
Pick a repository and a channel
Choose from the repositories the app can see, most recently pushed first, with paging and search. Then pick the channel: one button uses the channel /setup was run in.
- 04
Choose what to post
Commits, pull requests and releases are ticked by default, with workflow runs, the issue board and stars in the same menu. Confirm, and ForgeFeed posts a sample of the repository's latest activity, labelled as one.
Which should you use?
The webhook, if…
- You have one repository and one channel for all of it
- You want raw events and nothing else
- You can add the webhook to each repository yourself
ForgeFeed, if…
- Commits, pull requests, CI and releases should each have their own channel
- You want a live issue board instead of a message per issue event
- You want workflow runs that update from queued to finished
- You would rather run /setup than paste webhook URLs
Want the full side-by-side? ForgeFeed vs the GitHub Discord webhook
Connecting GitHub and Discord, answered
Yes. Create a webhook in a Discord channel, add /github to the end of its URL, and add that URL as a webhook in the repository's settings on GitHub with the content type set to application/json. GitHub then posts the events you choose into that one channel.
It is usually one of three things: the URL is missing /github at the end, the content type is not application/json, or the event is not one Discord's GitHub endpoint accepts, such as workflow_run. The webhook's Recent Deliveries tab on GitHub shows Discord's response to each delivery.
With webhooks, you add one webhook per channel in every repository, each set to its own events. With ForgeFeed, each tracker picks its own channel: /track commits can post to one channel while /track releases posts to another, and /trackers moves a tracker later.
Both do. A webhook added in a private repository's settings posts its events like any other. ForgeFeed works with any private repository you grant its GitHub App access to: your personal account on Free, and organizations too on Premium.
Not with the webhook: adding one takes admin on the repository. ForgeFeed can follow a public repository read-only once your server has a linked GitHub account. Add it with /repo add, and its commits, pull requests, releases, workflow runs, stars and issue board post from a check every 15 minutes. Comments, discussions, deployments and security alerts need access granted to the app.
On the ForgeFeed page, Link a different server with a code gives a single-use code that expires in 15 minutes. Enter it with /github link in a server you manage. The code is for someone with the same access to the account.
GitHub publishes official apps for Slack and Microsoft Teams. For Discord, the built-in route is the GitHub-compatible webhook that Discord provides, and bots such as ForgeFeed add channel routing and boards on top.
The webhook is free. ForgeFeed is free for one repository on your personal GitHub account, with up to 30 trackers. Premium is $4.99 a month for 10 repositories or $9.99 for 25.
Keep reading
- ForgeFeed vs the GitHub Discord webhookEvery difference between the two, row by row, including where the webhook is enough.
- Setup and command referenceEvery /setup step, all 20 commands, every tracker option, and the permissions the bot asks for.
- Use casesCommit, pull request and release notifications, CI alerts, live issue boards and more, each set up end to end.
Connect GitHub to Discord in one command.
Add ForgeFeed, run /setup, and pick which updates go to which channel from a menu. Free for one repository.
Need organizations or more repositories? Premium, from $4.99 a month for 10 repositories
Join the Discord servers already running ForgeFeed.