Turn Your Changelog into Social Posts
Shipstar converts your changelog into social posts automatically. Connect a GitHub repository and it reads the commits and pull requests of a period — seven days by default — and drafts an X/Twitter thread and a LinkedIn post as separate content types, written for the feed rather than copied from the changelog. Drafts wait in a review queue; approved X threads are posted to your connected X account on publish or on a schedule, and LinkedIn posts are ready for you to copy. It is built for developers and small product teams who ship constantly and post rarely. Start free: the Free plan includes 1,000 credits a month, a Twitter/X thread or LinkedIn post costs 25 credits, and Solo is $25/month (or $240/year) for 50,000 credits — enough to convert every changelog entry into social media posts.
From Changelog Entry to Post, Automatically
The gap between 'we shipped it' and 'we posted about it' is where most social momentum dies — someone has to notice the release, distill it, and write something feed-worthy. Shipstar closes the gap: the same Git activity that powers your changelog also generates social posts, so every meaningful change arrives pre-drafted for X. Publishing becomes a review decision instead of a writing task.
Convert a Changelog to Social Posts from GitHub
Install the Shipstar GitHub App on your organization (or connect through GitHub OAuth) and choose the repositories to track. A run reads one commit window — seven days by default for a manual or API run, while a schedule covers the gap to its previous occurrence, capped at 31 days — and produces one content type, so a weekly schedule for an X/Twitter thread and another for a LinkedIn post keeps both feeds moving from the same shipped work. You can scope a run to named repositories and override the project's voice preset or focus-and-exclusions instructions per run. The same generation is exposed over the public API and the MCP server, so a coding agent can convert the week's changelog into social posts as the last step of its own release loop. GitHub is the only source today; GitLab and Bitbucket are coming soon.
Written for the Feed, Not the Repo
A changelog entry and a social post do different jobs. The entry documents; the post has to earn a stop mid-scroll. Shipstar generates each format separately from the underlying changes — the post leads with the user benefit, drops the internal detail, and fits the platform's length and rhythm. It's a rewrite for the medium, not a syndicated copy-paste with a link.
A Build-in-Public Engine
Build-in-public works because steady visible progress compounds — followers, credibility, inbound interest. It fails because founders can't sustain the posting habit past week three. Shipstar makes the habit structural: as long as the team ships, the posts keep coming. Your commit history becomes a public narrative of momentum, with zero standing meetings about 'social content.'
Cadence Without a Social Media Manager
Consistency beats virality, and consistency is a scheduling problem. Review generated posts in batches, approve the good ones, and schedule them to publish automatically — a steady drumbeat instead of a burst after every release. Connect your X account once; Shipstar handles formatting and publishing. Slack and other channels can carry the same updates for your community spaces.
CLI Changelog-to-Social Scripts vs. a Hosted Pipeline
The open-source route exists. humanwhocodes/social-changelog, for example, is an npm CLI (also runnable as a GitHub Action) that reads a GitHub release and uses an LLM of your choosing — you bring your own OpenAI or Anthropic API key — to print one social post to the console for you to paste or pipe onward (as described in its README, September 2026). It fits when you already write release notes and want one post per release. A hosted pipeline like Shipstar — a hosted product, not open source — starts further back and goes further forward: it reads the commits and pull requests themselves rather than a release you have already written, rewrites separately for each channel, holds every draft in a review queue, schedules the cadence, and publishes to X without you managing API keys or a posting script. The same run can feed your changelog, release-notes email, and blog.
Why teams choose Shipstar
- Every shipped change arrives as a pre-drafted social post
- Posts rewritten for the feed — benefit-led, platform-length, no copy-paste
- Sustain build-in-public indefinitely, powered by actual shipping
- Review in batches, schedule the queue, keep a steady cadence
Frequently asked questions
How do I turn changelog entries into social posts?
Connect your GitHub repository and X account to Shipstar. The same shipped changes that generate your changelog also generate social posts, drafted for the feed. Review, approve, and schedule — Shipstar publishes them to X automatically.
Are the posts just changelog text with a link?
No. Social posts are generated as their own content type: benefit-first framing, platform-appropriate length, no internal jargon. The changelog documents the change; the post is written to earn attention for it.
Can I review posts before they go out?
Always. Generated posts wait in a review queue where you edit, approve, or reject. Approved posts can publish immediately or on a schedule, so you can batch a week of posts in one sitting.
Can Shipstar convert a changelog to social posts automatically?
Yes. Shipstar reads the commits and pull requests behind your changelog in GitHub and generates the social posts from them: an X/Twitter thread and a LinkedIn post, each written for its platform. Every draft waits for your review; approved X threads are posted to your connected X account automatically, on publish or on a schedule, while LinkedIn posts are generated for you to copy into LinkedIn. GitHub is the only source today, and the Free plan includes 1,000 credits a month.
Which social platforms are supported?
X (Twitter) is the destination Shipstar posts to automatically: connect your X account and approved threads are published on publish or on schedule. LinkedIn posts are a generated content type — Shipstar writes the post in a professional register and you copy it into LinkedIn; direct LinkedIn publishing is coming soon. Slack channels carry the daily and weekly product updates, and webhooks route content anywhere else. The same shipped changes can also feed your changelog page and email subscribers.
Explore more
Explore related pages
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds