A Buffer alternative for developers. It writes the posts too.
Buffer is a social media management tool: you write the posts, it queues them, publishes them across your networks and reports back on how they did. It is good at that. It assumes you turned up with something to say.
Buffer alternative
Is Merge & Tell a Buffer alternative?
For one kind of account, yes. If you post on your own and everything you post is about software you ship, Merge & Tell replaces Buffer. It reads your merged GitHub pull requests, and the ones worth announcing become posts sized for X, Bluesky, Mastodon, LinkedIn, Discord and Slack, or articles on your WordPress. Each draft waits for your approval by default (a network or rule you set to Publish skips that step), then publishes to your own accounts through its own queue, with posting slots and a minimum gap between posts. Buffer starts one step later: you write the post, and it schedules it.
It is not a replacement if you also post campaigns, events or anything on Instagram, TikTok or Facebook, if a team plans a shared calendar, or if engagement analytics is the number you manage to. Keep Buffer for that half and let this handle what you ship. Plans start at $29 a month, and the free trial does not expire. See pricing.
The short answer
Two halves of one problem
A scheduler solves when this goes out. Merge & Tell solves what goes out at all. If your marketing problem is that Tuesday’s post lands at a bad hour, that is a scheduling problem and you should buy a scheduler. If your marketing problem is that you shipped four things last week and wrote about none of them, no calendar is going to help, because the calendar is empty for a reason.
Merge & Tell reads your merged pull requests and writes the post. The input is a real diff, so the output is about something that actually happened, and a merge you were doing anyway is what starts it.
Why the category matters
The queue is not the hard part
Every publishing tool starts at the same moment: a human has decided there is something to say and has said it. That decision is the step that quietly does not happen when the person who would make it is also the person reviewing the PR, fixing the deploy and answering support.
So the tools stack up unused. An empty content calendar is not a product failure, it is the content-supply problem showing through the UI of something that was never meant to solve it.
The other half of that supply problem is knowing what not to say. Merge & Tell drops bot pull requests, dependency bumps and noise-only diffs before they reach a draft. Under ten meaningful lines the diff counts as trivial. A pin or the brief can still call that change major, and major user-facing news still gets a post. Chores, refactors and minor user-facing updates skip, and no post goes out for them. You batch by hand when you want one. A tool that turned every merge into a post would be worse than silence. How the filter works.
Side by side
Which tool does which job
| The job | A scheduler | Merge & Tell |
|---|---|---|
| Where a post comes from | You write it | A merged pull request and its diff |
| What starts the process | You opening the app | A GitHub webhook, on merge |
| Deciding something is not worth posting | You, by not writing it | The filter ladder, before a draft exists |
| Per-network copy | Usually one body, adapted by hand | Written per channel, to that network’s own limit |
| Who the copy is aimed at | Whoever you had in mind | A stored ICP, applied to every draft |
| Who appears to be speaking | The account you post from | A named voice, brand or person, resolved per channel. Copy in a person’s voice never auto-publishes |
| What it measures | Engagement on what you posted | How much of what it wrote you kept, and how much you rewrote |
| Networks | Broad, including the consumer ones | X, Bluesky, Mastodon, LinkedIn, Discord, Slack, WordPress, plus a changelog feed |
The last row is the one to read twice. Merge & Tell does not post to Instagram, TikTok, Facebook or Pinterest, and won’t. The people this is built for do not launch developer tools on Pinterest.
Honesty
Where they genuinely overlap
Merge & Tell publishes. Once a draft is approved it goes to your own connected accounts, through its own queue, with posting slots, a minimum gap between posts, retries with backoff and a stop button. That is scheduler work and it does it, so this is not a case of two tools that never touch.
In practice, if everything you post is about what you shipped, you probably do not need both. If you also run campaigns, seasonal content, event promotion or a brand presence on networks Merge & Tell does not touch, you do, and the two sit side by side without fighting, because it never posts to an account you have not connected to it. How the queue behaves.
Not this one
When Buffer is the right answer
Buy the scheduler, not this, if most of the following are true. Better to hear it here than in an email three weeks in.
- Your content is not about software you ship.
- Instagram, TikTok or Facebook is where your audience actually is.
- A team of marketers plans a content calendar together, week by week, around campaigns rather than around what shipped.
- Engagement analytics is the number you are managing to. Merge & Tell tracks a different number: whether the drafts were worth keeping.
- You are an agency running many client brands from one login.
None of that is a knock on the tool. It is a different job, and a tool that claims to do every job is lying about one of them.
Together
Running both
The clean division: ship-driven content comes from here, everything else comes from wherever you plan it. Nothing in the way it publishes assumes it is the only tool touching an account. It uses your tokens for the posts you approve, and nothing else. What happens to your tokens.
And if you want to see it before believing any of this, the bottom of the home page is Merge & Tell’s own accounts, live, posting what this wrote about its own merges.
Fill the queue first.
You were going to merge the PR anyway.