DevRelay turns released GitHub changes into reviewable launch drafts

DevRelay is an AI developer-relations tool for software teams that ship changes faster than they explain them. It watches selected GitHub repositories, gathers evidence for an announcement and drafts material for several channels. A person reviews the exact version before it can publish.

Wait for the release rather than the merge

The product distinguishes a merged pull request from a released feature. In its standard workflow, merged work waits until a GitHub release ships it. Teams releasing from a branch can instead configure a merge into their designated release branch as the release event. A plain push does not count.

DevRelay says it filters dependency bumps, typo fixes and test-only changes, then gathers the diff, linked issues, release notes and documentation for changes worth announcing. Its sample workspace is explicitly fictional, so the example posts should be treated as demonstrations of format rather than customer results.

Keep approval attached to the content

Drafts can include X and LinkedIn posts, changelog entries, documentation patches and tutorials. Approved documentation updates open a pull request for the team to review and merge. Changelog entries and tutorials can export as Markdown; newsletters are copied into the team's email tool rather than sent to a mailing list by DevRelay.

An approval applies to one version. Editing an approved draft makes the old approval stale. That distinction is useful when a last-minute wording change affects a feature claim or availability date.

Check permissions and the publishing plan

Setup involves installing the GitHub App, choosing repositories and adding product knowledge sources. Documentation pull requests need contents and pull-request write access on the chosen docs repository. Social connections are separate and optional.

The publisher advertises free drafting and review, with a paid plan for publishing. Before connecting a production repository, review the requested access and try one completed release through the approval inbox. Check that the announcement describes what users can actually access, and that the documentation patch belongs in the intended repository.