Announce new GitHub releases in Discord
The moment you publish a GitHub release, rewrite the notes for real humans and post them as a rich embed in your community Discord channel.
Integrations
GitHub
Discord
Type
Categories
- Engineering
- Product
When a new release is published on my GitHub repository, generate a community-facing changelog and announce it in Discord.
Trigger: a GitHub webhook on the release event, filtered to action = published (GitHub sends this outgoing webhook natively — no polling). Let me configure the source repository. The trigger payload gives you the release object directly (name, tag_name, html_url, body, author, prerelease, draft). If the body looks thin or the payload is missing anything you need, call GitHub's Get a Release to fetch the full release detail.
Rewrite the raw release notes as a friendly announcement aimed at end users, not developers. Lead with the headline features, use plain language, add a few tasteful emojis to break up sections, and drop internal refactor / dependency-bump / chore noise. Strip PR numbers (e.g. "(#1234)") and commit SHAs from the user-facing version — the link back to GitHub carries all of that for anyone who wants it. If the release is marked prerelease or draft, either skip it or clearly label it, depending on how I configure it.
Then use Discord's Send a Message to post the announcement as an embed in the announcement channel I configure. Set the embed title to the release name (fall back to the tag name if the name is empty), the description to the rewritten notes, the url to the release's html_url, and the footer to the version tag. Respect Discord's embed limits: description max 4,096 characters and total embed content max 6,000 characters. If the rewritten notes would exceed the description limit, trim cleanly at a section boundary and end with a link to the full release notes on GitHub.
If the target channel is a Discord announcement channel (channel type 5), also call Crosspost a Message on the message you just sent so it fans out to every server following the channel. If the channel is a regular text channel, skip the crosspost step.
Let me configure the source GitHub repository, the target Discord channel, whether prereleases and drafts should be announced, and any tone or brand-color preferences for the embed.
What it does
- Listens for the release event on your GitHub repo and picks up the notes as soon as you hit publish.
- Rewrites the raw changelog into a friendly announcement — headline features first, plain language, a few emojis, and none of the internal refactor noise.
- Posts the result to your chosen Discord channel as an embed with the release name, rewritten notes, a link back to GitHub, and the version tag in the footer.
- If the channel is an announcement channel, crossposts the message so every server following you sees it too.
What you’ll need
- A GitHub repository you can add a webhook to (public or private, both fine).
- A Discord server where you can post messages and pick the target channel.
- Any brand color or emoji preferences you want the announcement to use.
How to customize it
- Point it at a different repository or a different Discord channel at any time.
- Adjust the tone — playful, professional, technical-lite — and which sections get dropped from the notes.
- Turn the auto-crosspost on or off depending on whether your channel follows other servers.
Use cases
- Notifications & Alerts
- Content Generation
