Broadcast to Slack
Release notes in Slack, without writing them.
Tag a release and Yanib drafts the story from your actual commits and PRs. Approve it once, it lands in the Slack channels you chose, formatted for Slack, alongside every other channel you publish to.
Free forever. No credit card.
How it works
Three steps. Two minutes.
Connect
Sign in with GitHub or GitLab and connect a repo, the webhook installs itself. Add your Slack channel with an incoming webhook URL, once.
Review
Every release tag becomes a structured draft, written from the real diff. Edit it, or let auto publish skip the review for low stakes repos.
Broadcast
One publish posts to Slack and every other channel you've linked, story page, email, Discord, GitHub Releases, at the same moment.
Why the broadcasting layer
Slack is one spoke of nine. Every channel gets the same reviewed update, from one publish.
- Per repo routing: send the platform repo to #platform and the app repo to #frontend
- A one line release summary, formatted for Slack, not a wall of markdown
- The release card image attaches automatically when your story page is public
- Slack is one spoke of nine, the same publish reaches every channel at once
Frequently asked questions
Do I need to build or install a Slack app?
No. Yanib posts through a standard Slack incoming webhook, create one in your Slack workspace settings, paste the URL into Yanib, and pick which repos route to it.
Can different repos post to different channels?
Yes. Integrations are linked per repo, so each repo decides which Slack channels (and which other channels) its releases reach.
What does the Slack message contain?
The release title, a one line AI summary of what shipped, and a link to the full story. If your public story page is enabled, the release card image is attached too.
Does Slack publishing block the rest?
No. Publishing is resilient by design, every channel is delivered independently, so one webhook hiccup never holds back the story page, email, or GitHub Release.