PR to LinkedIn post generator

Paste a GitHub pull request and turn it into a LinkedIn post for developers: a hook that fits above "see more", what changed, how to use it and the link. Free, no sign-up.

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

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

02

Get a post

A hook short enough to show above "see more", then what changed, how to use it, and the link.

03

Make it yours

Add a sentence only you can write: why you built it, or who asked for it.

How developers read product updates on LinkedIn

LinkedIn shows the first few lines of a post and folds the rest behind “…see more”. Most people decide from those lines alone. For a product update that means:

  • First line: the change and who it helps. “Postgres users can now branch a database per pull request.”
  • Then the details, short lines with white space between them. Use a short list for more than two points.
  • End with one link to the docs or release notes, and one clear next step.

Preview where your hook gets cut with the LinkedIn text formatter.

Company page or personal profile?

Posts from the engineer who built the feature usually reach more people than the same text from a company page, because people follow people. A common pattern: the builder posts the story, and the company page reshares it.

DevRelay does this for every release. DevRelay drafts LinkedIn posts from every released change, grounded in your docs and brand, and posts them to your connected account once you approve. Start free.
FAQ

Questions about this tool.

01How long should a LinkedIn product post be?

Long enough to explain the change, usually 600 to 1,300 characters. LinkedIn allows up to 3,000. What matters most is the first two lines.

02Does it add hashtags or emoji?

At most one hashtag and no emoji walls. Developer audiences tend to skip posts that look like marketing.

03Is my input stored?

No. The pull request text goes to the model to write the draft and is not kept.

04Does it work for private repositories?

Yes, when you paste the pull request (title, description and its .diff page). DevRelay, the product, connects to private repositories with a GitHub App.

More free tools

All tools
Announce · AIPR to X post generatorPaste a GitHub pull request, get an X post and a threadOpen the tool Announce · AIShow HN title generatorPlain, specific Show HN titles, checked against HN conventionsOpen the tool Announce · In browserX character counter and thread splitterCount characters the way X does and split long text into a threadOpen the tool

Or let every release announce itself.

DevRelay drafts LinkedIn posts from every released change, grounded in your docs and brand, and posts them to your connected account once you approve.

Start free More free tools

No credit card · Nothing posts without your approval