Turn merged PRs into LinkedIn posts and tweets
ShipPost takes a merged GitHub pull request and drafts a LinkedIn post or a tweet about what you shipped — in your voice, not a robot's.
Open ShipPost Opens shippost.lol in a new tab
You shipped something good this week. It’s sitting in a merged pull request, where roughly nobody outside your repo will ever see it. Turning that into a post means context-switching out of code, staring at an empty box, and trying to sound interesting about a diff.
ShipPost does that part for you. Give it a merged pull request and it drafts a LinkedIn post and a tweet about what you actually shipped.
Why the merged PR
Most “build in public” tools start from commits. Commits are a running monologue — half-finished, often cryptic, rarely the story. A merged pull request is the opposite: a complete, reviewed, shipped change with a title and a description that already explain the point. It’s the right unit to write about, and it’s where ShipPost begins.
Your voice, your key
The drafts are meant to read like a developer wrote them — not a breathless content bot. You edit before anything goes out; ShipPost just gets you past the blank page.
It runs on your own model API key. Your code and your key stay with you — nothing is resold, and nothing is proxied through a middleman. That’s a deliberate choice, not a line on a roadmap.
Who it’s for
Developers and indie makers who ship more than they post. If “build in public” keeps losing to “actually build the thing,” this is the bit that closes the gap.
The longer argument is in turn merged PRs into launch posts, and the studio thinking in small, honest software.
What it does
- Starts from the merge Point it at a merged pull request — the unit of actual shipped work — not a noisy stream of half-finished commits.
- Sounds like you Drafts read like a developer wrote them, not a marketing bot. Edit and post, or use them as a starting point.
- LinkedIn and X Get a longer LinkedIn post and a short tweet from the same PR, ready to paste.
- Bring your own key Use your own model API key. Your code and your key stay with you — nothing is resold or proxied through a middleman.
Questions
- Can I turn a GitHub PR into a LinkedIn post?
- Yes — that's exactly what ShipPost does. Give it a merged pull request and it drafts a LinkedIn post about what you shipped.
- Does it write tweets too?
- Yes. You get a short version for X alongside the longer LinkedIn draft.
- What does bring your own key mean?
- You connect your own model API key. ShipPost uses it to generate the drafts; your key and your code aren't resold or routed through a third party.
- How is this different from a commit-to-post tool?
- Commits are noisy and often half-finished. A merged pull request is a complete, reviewed, shipped change — a much better unit to write about. ShipPost works from the PR.
- Will the posts sound like AI?
- They're written to sound like a developer, not a content bot — and you edit before anything goes out.
- Who makes ShipPost?
- ShipPost is built by Drizzlelabs, an independent UK software studio.