Every release you ship, turned into
an X thread.a changelog entry.a docs update.a LinkedIn post.a newsletter.a Product Hunt kit.a tutorial.

No. Nothing is published without a human approving that exact version. After approval, X and LinkedIn posts go out immediately or at the time you scheduled. An approved docs update opens a pull request on your docs repo for you to merge. Changelog entries and blog posts go to your hosted changelog page, or you export them as Markdown for your own site or CMS, along with tutorials.

No. Merged pull requests are held until a GitHub release ships them. If you release from a branch instead of tags, set the repo to branch mode and a merge into that branch counts as the release. A plain push never does.

Security-sensitive changes are marked BLOCK and never drafted automatically. They show up on your Today page for a human to decide. An admin can still ask for a draft, with a written reason that is logged.

Drafts are written from evidence collected for that change: the diff, release notes, linked issues and your docs. Every draft then goes through hard gates. Claims without evidence, feature names or numbers that don't appear in the evidence, beta features called GA, and unsupported "first" or funding claims all fail, and the draft is repaired or held.

DevRelay routes each task to a model by role: one decides what's worth announcing (it never writes prose), one extracts facts, one writes. Secrets are redacted before any model call, and content from your repos and websites is always treated as data, not instructions.

You install the DevRelay GitHub App and choose which repositories it watches. You add your website, docs and blog as knowledge sources. X, LinkedIn and Slack are optional and connect with their own sign-in flows. For docs pull requests, the GitHub App also needs write access to contents and pull requests on your docs repo. You can disconnect any of them from Settings.

Yes, on the DevRelay plan. An approved docs update is committed to a new branch in the docs repo you pick and opened as a pull request; you review and merge it on GitHub. Launch images are rendered from a brief built from your brand, and an approved image goes out with the X and LinkedIn posts. Launch videos (up to 10 a month) are made by our team from the script within 24 hours, and the app shows when one is in production.

Yes. Turn on the weekly recap, the monthly one or both in Settings. DevRelay drafts a “What shipped” post, an X thread, a LinkedIn post and a newsletter you copy into your email tool. Security fixes, ignored and reverted changes are left out, and the drafts wait in the inbox for approval like everything else.

Posts about features you already have. DevRelay builds a feature catalog from your docs and website and proposes how-tos, tips, use cases and answers to questions people ask. Turn on the weekly plan, set how many posts a week you want per channel, and it fills only the slots your releases left free. Nothing is ever written as news unless it was released in the last two weeks.

Short educational videos of your AI avatar, made from your photo and a voice you pick, that teach your niche rather than announce a release. DevRelay suggests five topics a week; approve one and our team makes the clip within 24 hours, with a title and caption. You download it and post it. 10 a month on the DevRelay plan.

A generator turns commits into a list. DevRelay decides which changes deserve an announcement at all, waits for the release, writes for each channel in your voice, checks every claim against your code, and learns from your edits.

Software companies that ship often and build on GitHub: SaaS products, APIs and developer tools. Drafts are written for the people who use your product, in plain words. It fits best when nobody owns product announcements, or one person covers docs, community and social.