The right way to handpick commits for a post (not everything ships)

Over a busy week you might land thirty or forty commits. Dependency bumps, a typo fix in a log line, a refactor nobody will ever see, and—buried in the middle—the one feature your customers have been asking for. If you post about all of it, you bury the signal. If you post about none of it, nobody hears the news.

The skill isn't generating content. It's choosing which commits are worth talking about and letting the rest stay quiet. MarketMee gives you a precise way to do exactly that with Pick commits, so a post reflects the changes a user can actually feel, not your entire Git log.

Start by analyzing the repo

Everything begins in the GitHub section of the sidebar.

1. Open GitHub and click Connect GitHub if you haven't linked an account yet. MarketMee supports multiple GitHub accounts, including organization repositories.
2. Select a repository from the dropdown. As soon as you do, MarketMee analyzes the last 50 commits immediately.
3. Browse the analyzed list. For each commit you get a plain-English summary and a labelled changelog—features, fixes, improvements, refactors, docs—so you can tell at a glance what each change actually was.

Those labels are the whole point. A wall of commit hashes tells you nothing about what's post-worthy. A list that says "feature," "fix," "refactor," "docs" lets you skim for the handful of entries that matter.

Commit analysis and changelogs are free—they don't cost any tokens—so there's no penalty for connecting a repo just to see what you've shipped.

Use Pick commits to go beyond the default list

The analyzed list shows your recent history, but the real control is the Pick commits button. Click it and you can select specific commits from any branch, not just main.

This matters more than it sounds. A lot of the good stuff lands on a feature branch days before it reaches main, and plenty of teams squash-merge in a way that hides the original story. Pick commits lets you reach into the branch where the work actually happened and choose the commits that tell it best.

A few limits to keep in mind:

• You can select a maximum of 20 commits at once.
• Selection works across any branch, so you're never stuck with just your default branch.
• There's no requirement to pick a contiguous range—grab the three commits that built the feature and skip the six that fixed its tests.

How to decide what makes the cut

The filter is simple: could a user notice this without reading the code? If the answer is yes, it's a candidate. If the answer is no, let it stay in the changelog where it belongs.

Keep:

• New features and new settings a customer can see or toggle
• Fixes to bugs people actually hit
• Noticeable improvements—speed, reliability, a smoother flow

Skip:

• Internal refactors that change nothing visible
• Dependency bumps and version housekeeping
• Docs-only changes and test scaffolding (unless the docs are the product)

You don't have to be ruthless about keeping it to a single commit. A good post often stitches together a small cluster—the two or three commits that, together, add up to one story a reader can follow. The 20-commit ceiling is generous enough that your real constraint is editorial, not technical: what's the tightest set of changes that makes one clear point?

Turn the selected commits into a post

Once you've picked your commits, you're ready to generate. From the GitHub section, with a repository and commits selected, click Generate posts and choose:

• Number of post variants: 1–5 versions of the same post
• Images per post: 1–8 images for each version

MarketMee then generates the variants side by side, so you can compare different angles on the same set of commits instead of committing to the first draft. The token cost is shown before you generate anything, so there are no surprises.

Refine before you publish

For each variant you can:

• Read the caption and review the images.
• Edit the caption by hand, or click Rewrite to ask AI to push it in a specific direction.
• Click any image to edit it—describe the change in plain English, like "use darker colours," and MarketMee regenerates it.
• Delete images you don't want. You can keep up to 4 images per post (or 1 video if you're using a video project instead).

Caption writing and rewrites don't cost tokens; image edits and regenerations do, and the cost is always shown before you apply it.

Once you've picked your favourite variant, choose how it goes out:

• Publish now sends it immediately.
• Pick a date and time schedules it for later.
• Add to queue drops it into your next open schedule slot.

Then select which connected social accounts should receive it. Posts from handpicked commits land in the same queue and Timeline as everything else, so your manual picks live alongside anything Autopilot produced.

When to handpick vs. let Autopilot run

Handpicking is the right tool when you care about a specific launch: a flagship feature, a fix your community has been waiting on, or a milestone worth framing deliberately. You're in control of exactly which commits tell the story and how the final post reads.

If you'd rather keep a steady drumbeat without curating every time, Autopilot watches your repositories and creates posts from new commits on a schedule—but even then, the instinct behind Pick commits is the same: not everything ships to your audience. Handpicking is simply you doing that editing by hand, for the moments that deserve it.

The takeaway

Your repository is a stream of changes, but your feed shouldn't be. Use the analyzed commit list to see what you've shipped, use Pick commits to reach across any branch and select only the changes a user can feel, and keep your selection tight enough to make one clear point. Then generate a few variants, tidy the caption and images, and schedule it.

Ready to try it on your own repo? Open the GitHub section at marketmee.app and pick the commits worth announcing.