PR to X post generator

Paste a GitHub pull request and get a multi-line X post and a 3 to 5 post thread about the change, written for your users. Works for private repos. Free.

AI · Free · No sign-up

How to copy a pull request from GitHub

  1. Open the pull request on GitHub.
  2. Copy its title and description (the first comment) into the first box, with the title on the first line.
  3. For a more specific post, add .diff to the end of the pull request's address (github.com/owner/repo/pull/123.diff), select everything (Ctrl+A or ⌘A), copy it and paste it into the second box.
The .diff page of the pull request. Works for private repositories too.
A help, docs or product page. GitHub links are left out: your customers can't open them.
Is it released?

Nothing you paste is stored, and secrets are redacted before the text reaches the model.

How to use it

01

Paste the pull request

Copy its title and description from GitHub, and the .diff page for more detail.

02

We read the change

The title, description and, if you paste it, the diff and its changed files. Nothing else is guessed.

03

Edit and post

You get one post and a short thread, each laid out in short lines and counted the way X counts. Copy the one you like.

What makes a good feature announcement on X

People scroll past launch copy and stop for specifics. A post that works says what changed, why a reader would care, and where to try it, in that order:

  • Lead with the capability, not the version number. “You can now paginate events with a cursor” beats “v2.4 is out”.
  • Break it into short lines: what's new, what you can do now, then two or three short benefits. A wall of text gets skipped.
  • Link to your help or product page, not the pull request or release: your customers can't open your repository. Put the link last so the preview card sits under the text.
  • Skip hype words. “Blazing fast” reads as filler; “p95 down from 41s to 6s” reads as news, if you measured it.

Single post or thread?

Use a single post for small fixes and focused features. Use a thread when the change needs context: a migration, a new API with several options, or a before-and-after. Keep threads to three to five posts, and make the first one stand on its own, because most readers never expand the thread.

Merged is not released

A merged pull request is not always in a release people can install. If you mark a pull request “Not yet”, this tool writes it as coming soon instead of available. Check with the PR release finder before you announce, and count the final text with the X character counter. To have a post drafted from every release instead, compare the tools that turn GitHub PRs into X posts.

DevRelay does this for every release. DevRelay watches your repositories, waits until a change is actually released, and drafts the X post, LinkedIn post and changelog in your voice for you to approve. Start free.
FAQ

Questions about this tool.

01Does it work with private repositories?

Yes, if you paste the pull request: copy its title and description, and its .diff page (add .diff to the end of the PR's address while signed in to GitHub). DevRelay, the product, connects to private repositories through a GitHub App.

02Is my input stored?

No. What you paste is sent to the model to write the draft, with secrets redacted first, and the text is returned to you. We keep a count of calls for rate limits, not your input.

03Why is there a limit?

Each draft costs a model call. To keep the tool free, each visitor gets a few drafts an hour and there is a daily cap across everyone.

04Can it write in my brand voice?

Not this free tool: it writes in a plain, direct voice. DevRelay learns your voice from your site, docs and the edits you make to drafts.

Or let every release announce itself.

DevRelay watches your repositories, waits until a change is actually released, and drafts the X post, LinkedIn post and changelog in your voice for you to approve.

No credit card · Nothing posts without your approval