Announce new GitHub releases in Discord

PromptCreate

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 does this prompt do?

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 do I need to use this?

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 can I 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.

FAQs

Does this work for private GitHub repos?

Yes. As long as the workflow has access to the repository, private releases are announced the same way as public ones.

Will draft or pre-release publishes get announced?

You can tell it to only fire on full releases, or include pre-releases and draft publishes if you want your community to see early builds.

What happens if the release notes are really long?

Discord caps embed descriptions at 4,096 characters. The announcement gets trimmed cleanly with a link back to the full release notes on GitHub.

Can it post to more than one Discord channel?

Yes. You can add extra channels — for example a public community channel plus a private staff-only channel — and each one gets its own copy.

Does the community see PR numbers and commit hashes?

No. Those get stripped from the announcement so the message reads like a product update, not a git log. The full technical notes stay on GitHub.

Related templates

Open a Heroku release war room the moment production looks wrong

See every recent deploy across all your Heroku apps in one timeline, then roll back, restart, or file an incident without leaving the screen.

App

See what Hacker News really thinks of the tools in your stack

Every tool you run or are weighing up, with the Hacker News threads that actually mattered, project health beside them, and a written verdict you keep.

+1

App

See and fix Terraform variable drift across every workspace

One matrix that shows every workspace variable side by side, flags what is missing or mismatched, and fixes it only after you approve each change.

App

A docs coverage board that catches what shipped undocumented

See everything engineering shipped next to the docs pages that cover it, so the work nobody labelled stops slipping through.

App

A technology radar board your architecture group works out of

Every library you have adopted, are trialing, are assessing or have put on hold, on one board, with live research and a written recommendation on each card.