Use Case
Turn your pull requests into posts
You're shipping features, fixing bugs, and refactoring code every week. ShipPost turns that merge history into LinkedIn posts and tweets that actually sound like you wrote them.
Try it freeHow it works
From merged PR to published post
01
Connect GitHub
Add your GitHub token and username in settings. ShipPost uses your existing access — no OAuth apps or extra permissions needed.
02
Scan your PRs
Hit scan and ShipPost fetches your recently merged pull requests. Pick the one you want to post about.
03
Generate posts
ShipPost reads the PR context — title, description, diff stats, labels — and generates multiple post variations for LinkedIn and X.
04
Copy and ship
Pick your favorite variation, tweak it if you want, and paste it straight into LinkedIn or X. Done in under a minute.
Example
What it looks like in practice
Your PR
feat: add real-time collaboration to editor
Implements CRDT-based real-time editing with cursor presence and conflict resolution. Replaces the old polling approach.
Generated post
Just shipped real-time collaboration in our editor. Replaced
polling with CRDTs — conflict resolution that actually works
without a central server.
The old approach? Poll every 2 seconds, hope for the best, show a "someone
else is editing" banner when it inevitably broke.
The new approach? Cursor presence, live edits, zero conflicts. 847
lines of new code, but it replaced a system that was 10x more complex
to maintain.
Sometimes the best refactor is throwing away the abstraction entirely.
Why PRs make great content
They're real
Unlike "thought leadership" posts invented from thin air, PRs are actual work you did. That specificity is what makes posts interesting. People can tell the difference between "I think microservices are overrated" and "We just migrated 3 services back to a monolith — here's why."
They're already written
The hardest part of posting is starting from a blank page. Your PR already has a title, a description, and context. ShipPost just translates that from "developer writing for reviewers" to "developer writing for their network."
They're consistent
You merge PRs regularly. That means you have a built-in content calendar. No need to sit around thinking "what should I post about?" — just scan your recent merges and pick the most interesting one.
Related reading
FAQ
Common questions
Which GitHub repos does ShipPost support? +
Any public or private repo you have access to. ShipPost uses your personal GitHub token, so it can see everything you can see. It scans for merged PRs where you're the author.
What information does ShipPost pull from a PR? +
The PR title, description, labels, diff stats (files changed, additions, deletions), and the merge date. It uses all of this to understand the context of your change and write about the idea — not the commit.
Can I edit the generated posts before publishing? +
Yes. ShipPost generates multiple variations for each PR, and you can copy, edit, and tweak any of them before posting. The generated text is a starting point, not a final draft.
Does it work for PRs I merged months ago? +
ShipPost scans your recent merge history based on your GitHub username. It's designed for recent PRs, but you can scan further back depending on the repo's history.
Is my GitHub token stored securely? +
Your GitHub token is encrypted at rest using AES-256-GCM and stored in your Convex user settings. It's only ever read server-side during PR scans — never sent to the browser.
Your PRs deserve an audience
Connect GitHub, scan your merges, and get posts ready to publish.
Get started freeNo credit card. No subscription. Bring your own API key.