Merge & Tell

“Booooorrrrring.”

Your customers, on what you shipped this month

Illustrated nerdy factory of robots and engineers stacking pull-request boxes beside a sunny cafe of sad bored customers with phones and a laptopBefore

Your team ships all week. Customers find out from a Slack thread somebody forwarded, a sales call that happened to mention it, or a support ticket asking for a feature that shipped last month.

Merge & Tell reads every pull request your team merges and drafts the update you would have written, if anyone had the time.

The same factory and cafe, with the Merge & Tell logo bridging them in orange light while versioned product updates reach smiling customersAfter

Same merges. Each one arrives as an update written for the customers it matters to. At first it waits for you. Once the drafts keep going out as written, it goes out on its own, the week the change ships.

Start freeTry it on a real PR, no signup

Whoever has GitHub access connects it once. Nobody on your team has to read a diff.

One merge, three jobs

Everyone who talks to customers gets the part they need.

Launch copy that is already written.

LinkedIn, X, Bluesky and Threads posts, drafted from the diff for the buyer you named and in the voice you chose, then gathered into the next newsletter issue. It goes out on its own, or waits for you to edit it first. Small fixes wait for a batch you build from several merges.

How it works for launches

Lands in

  • LinkedIn
  • X
  • Bluesky
  • Threads
  • Newsletter

Before and after

The PR is the brief. The entry writes itself.

larkspur/app · #482 · merged by dev-priyafeat(auth): SAML SSO + SCIM deprovisioning for workspace admins+1,204−8831 files
Changelogv2.4.1Went out on its own

Single sign-on for your whole team. Workspace admins can now connect Okta, Azure AD or any SAML 2.0 provider from Settings → Security. New hires land in the right workspace on their first sign-in, and when someone leaves, removing them in your identity provider removes them here too.

Written for: IT admins at 50–500 person companies

An example merge and the entry drafted from it. Not a real customer's.

Sign-off

Your team merges. You decide what goes out on its own.

  • Whoever merges

    Merges, like always

    No new process, no brief to write. The pull request is the brief.

  • Approver teams

    Sign off on a channel

    Put a channel under a team and its copy waits for someone on that team. Whoever merged the change can't approve the post about it.

  • On the draft

    Comment or request changes

    Leave the note on the draft, not in a thread nobody can find later. A change request stays on it until the copy is edited.

  • Slack

    Approve without opening the app

    The card lands in your channel. Approve, request changes, or open it in the app.

Every post that waits for a person counts against the Autopilot bar, and the app names the next channel that could go out on its own. How sign-off works

The Merge & Tell dashboard: what needs a person, this week’s merged PRs against what customers were told, and what goes out next.

Reads from GitHub · publishes to the accounts your team already runs

  • GitHub
  • LinkedIn
  • X
  • Bluesky
  • Mastodon
  • Threads
  • Slack
  • Discord
  • WordPress
  • Newsletter

Receipts

It runs on itself.

Everything below was written by Merge & Tell from a merged pull request in this repository, and published to its own accounts. Live off each network’s public API, not a screenshot and not curated.

Tell customers what changed, the week it changed.

Free for one repo: 10 merged PRs and 25 drafts a month. No card, no expiry.

Start free