Merge & Tell
Live demo

See what it writes about a real pull request

Tell it what you sell and who buys it, paste any public GitHub PR, and it writes the posts. This is the same generator the app runs on a merge, not a recording of one. Nothing is published, nothing is saved, and you do not need an account.

Want it pointed at a private repo instead? Sign in and install the GitHub App. That is the only way anything here reaches a repo the public cannot read.

Step one

Say what you sell, and who buys it

This is the part that does the work. The same pull request written for a platform team and for a finance lead produces two different posts, and these boxes are the only thing that decides which one you get. They start filled in with a worked example. Change as much or as little as you like.

Optional shortcut: this reads your home, pricing and about pages and fills everything below in. Nothing is saved.

Positioning

What the thing is. Named in the copy, and never guessed at.

Left empty, the drafts carry no link.

One or two sentences. The single field that most changes what comes back.

Steers the framing. Never quoted into the copy.

The reader

An ICP, which is just a written-down description of your ideal customer. The copy is aimed at this person and nobody else. One box, because this is the one that changes the output most and the rest can be inferred from it.

Step two

Point it at a pull request

Any public GitHub PR, yours or somebody else’s. The demo reads it the way a logged-out visitor to GitHub would, so a private repo is not something it can see.

Or borrow one of these:

  • . A framework change with a big diff and a terse description.
  • . A product change in a monorepo, the shape most teams actually merge.
  • . A small, user-facing fix. The hardest kind to write a post about.

Takes about twenty seconds. Nothing is published, nothing is saved, and no account is created.

Try it on a pull request — Merge & Tell