Not a scheduler. A supply of things to schedule.
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.
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.
We read your merged pull requests and write 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, noise-only diffs and changes under ten meaningful lines before they ever reach a draft, and holds the small survivors for a weekly roundup rather than dribbling them out one at a time. 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, plus a changelog feed |
The last row is the one to read twice. We do not support Instagram, TikTok, Facebook or Pinterest, and we are not planning to. The people this is built for do not launch developer tools on Pinterest.
Honesty
Where we genuinely overlap
We publish. Once a draft is approved it goes to your own connected accounts, through our own queue, with posting slots, a minimum gap between posts, retries with backoff and a stop button. That is scheduler work and we do 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 we do not touch, you do, and the two sit side by side without fighting, because we never post to an account you have not connected to us. How the queue behaves.
Not us
When Buffer is the right answer
Buy the scheduler, not this, if most of the following are true. We would rather say 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 calendar together and needs seats, roles and shared drafts.
- Engagement analytics is the number you are managing to. Ours is 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 we publish assumes we are the only tool touching an account. The tokens are ours to use for the posts you approve, and nothing else. What we do with your tokens.
And if you want to see it before believing any of this, the bottom of the home page is our own accounts, live, posting what this wrote about its own merges.
Fill the queue first.
You were going to merge the PR anyway.