Skip to content
LaunchMyServer

GitHub integration for Discord channels

Updated · Integrations

Create a webhook in the Discord channel, copy its URL, add /github to the end, and paste it as the Payload URL in your GitHub repository's Settings > Webhooks with content type application/json. GitHub events such as pushes, issues, pull requests and releases then post into that channel without any bot.

Ways to get GitHub activity into Discord
MethodSetupControl over messagesBest for
Discord webhook URL + /githubRepo Settings > WebhooksPick events; Discord formats themMost projects
GitHub Actions step posting to a webhookWorkflow YAML + webhook secretFull control of message textRelease notes, deploy notices
Organization-level webhookOrg Settings > WebhooksSame events across all reposMulti-repo orgs
Zapier GitHub -> DiscordZapierTemplated messages, filtersNon-developers, selective alerts
Third-party GitHub botBot dashboardVaries by botLinking issues from chat

Step by step: GitHub webhook to a Discord channel

Keep the webhook URL secret; anyone who has it can post in the channel.

  1. In Discord, open the channel's settings > Integrations > Webhooks, create a webhook (for example "GitHub") and copy the URL.
  2. Append /github to the URL: https://discord.com/api/webhooks/<id>/<token>/github.
  3. In GitHub, open the repository's Settings > Webhooks > Add webhook.
  4. Paste the URL as Payload URL and set Content type to application/json.
  5. Choose individual events (push, pull requests, issues, releases) rather than everything, then save. GitHub sends a ping event you should see in Discord.

Channels for a developer or open-source community

  • #announcements: releases only (one webhook filtered to release events).
  • #github-feed: pushes, PRs and issues; make it read-only for members so chat stays clean.
  • #help: a forum channel with tags like bug, question, solved, so answers are searchable.
  • #contributors: a private channel for maintainers and a Contributor role.
  • #showcase: what people built with the project.
  • Office hours or community calls as scheduled events in a Stage or voice channel.

Discord vs GitHub Discussions for open source

GitHub Discussions lives next to the code, is indexed by search engines, supports categories like Q&A with marked answers, and suits long-lived, searchable questions and RFC-style decisions. Discord is better for real-time help, voice calls and building a social community around the project, but chat history is harder to search and is not public on the web.

Many projects use both: Discussions for anything that should be findable later, Discord for conversation, with a rule that resolved Discord answers become a Discussion or docs page.

Quick answers

Github integration for discord channels?
Use a Discord channel webhook URL with /github appended as the Payload URL of a GitHub repository or organization webhook, content type application/json, and select the events you want.
Discord vs github discussions for open source?
Use GitHub Discussions for searchable Q&A and decisions tied to the repo, and Discord for real-time chat, voice and community. Many projects run both and move resolved answers into Discussions or docs.
Why is my GitHub webhook not posting to Discord?
Check that the URL ends in /github, the content type is application/json, and the webhook was not deleted in Discord. GitHub's Recent Deliveries tab on the webhook shows the response for each event.
Can I customize the message format?
Not with the /github endpoint; Discord formats GitHub's events. For custom text, use a GitHub Actions step or Zapier to post to a normal Discord webhook URL.

What to do next

Our SaaS customer community template includes announcements, a forum help desk and contributor roles you can wire GitHub into.

Related guides

Sources

Checked: . Discord changes features and menus often; if something looks different, the official help center is the source of truth. LaunchMyServer is not affiliated with Discord.