Knows what belongs together
Related work can deepen the same story days later. Different work starts a new one.
GitHub → posts, without the commit spam
Turn GitHub work into posts worth sharing.
Little Posts connects related commits and pull requests, even days apart, finds the story underneath, and gives you five distinct drafts. No more robotic posts for every commit.
14-day trial Selected repositories only Nothing posts automatically
Little Posts knows what belongs together.
Other apps make one post per GitHub event.
little-posts/onboarding 4 GitHub changes across 5 days
- Day 1
a3f7c2Connect GitHub OAuth - Day 2
8be214Add repository selection - Day 4
#148Recover failed first sync - Day 5
c91d08Handle retries without dead ends
Related changes become one evolving story with five angles.
1 evolving story · 5 drafts
GitHub onboarding is now working end to end. You can connect an account, choose the repositories you want Little Posts to watch, and recover cleanly if a sync fails. The setup flow now gets builders to their first real draft without the old dead ends.
A reliable sync flow is less about the happy path than the boundaries around it. I tied OAuth callbacks, repository selection, retry handling, and onboarding recovery into one stateful flow. Each stage now returns enough context for the next step to resume instead of sending the user back to zero.
The most frustrating onboarding bug looked random: a failed first sync could leave the setup screen with nowhere to go. The real issue was state recovery across OAuth, repository selection, and the retry path. Making those transitions explicit removed the dead end and made failures recoverable.
I kept treating GitHub connection as setup plumbing. It is actually the first trust test of the product. If Little Posts is going to turn someone's work into something worth sharing, connecting that work has to feel calm, selective, and reversible. This pass finally feels closer to that standard.
A major piece of Little Posts is now connected end to end. GitHub OAuth, repository selection, sync recovery, and retry handling are all working together. Builders can move from choosing a repo to seeing their first draft without getting trapped in setup.
Four changes become four separate posts.
4 GitHub events 4 separate posts
-
a3f7c2“Connected GitHub authentication with OAuth.”
-
8be214“Added repository selection so users can choose which repos to connect.”
-
#148“Improved recovery when the first sync fails.”
-
c91d08“Improved GitHub sync retry handling so failed requests recover more reliably.”
One early builder, in his own words
A record of the work and a way to bring people along.
Nate Early Little Posts user
“I have been looking for something to help me keep a record of what has been going into my codebase and little posts does just that. It helps you remember things more detailed when you push them. As well as keep your followers updated. Its perfect for the person building in public like me !”
Keep a record of the codebase Remember the details Keep followers updated
Real review. Real builder. No anonymous logo wall.
Product-by-product
Compare the tools directly.
Comparison checked August 5, 2026. Products change, so verify current details before relying on this comparison.
| What matters | Blurt | LaunchLogs | Postezi | Little Posts |
|---|---|---|---|---|
| What it organizes | Commits, merges, releases | Daily GitHub activity | Pushes, PRs, releases | Related work across time |
| Context model | Reads the event diff | Daily progress summaries | Event diff + configured context | Related work, understood over time |
| Choice from one story | One primary draft flow | Summary and social post | Platform-formatted drafts | Five editorial angles |
| Publishing today | Bluesky | X, LinkedIn, public profile | Bluesky, LinkedIn, X via BYOK | Edit or copy anywhereX Autopilot coming soon |
| Best when | Bluesky is your home | You want daily consistency | You want multi-platform value | Story quality and choice matter |
They help distribute posts. Little Posts knows what belongs together and builds each story over time.
The difference is not more posts
GitHub records the changes. Little Posts finds the story.
A feature rarely arrives in one perfect commit. It grows through the fix, the tradeoff, the refactor, and the pull request that finally ties it together.
Little Posts decides what belongs together. Related work deepens the story, even days later. Different work starts a new one. The result is meaningful progress, not a stream of dressed-up commit messages.
Find the stories in my GitHub work Editorial choice, not paraphrases
Choose the progress, technical, debugging, founder, or milestone angle that fits the moment.
Grounded in the real work
Every story stays attached to the GitHub activity that gave it meaning.
Five doors into the same story
One body of work should not force one voice.
The facts stay fixed. The angle changes with what you want your audience to understand.
- 01 Shipping update
Show the progress that is now real.
- 02 Technical insight
Share the thinking and tradeoffs behind it.
- 03 Debugging reflection
Tell the hunt behind the fix.
- 04 Founder reflection
Give the work its human meaning.
- 05 Milestone update
Mark the checkpoint worth remembering.
Built around your judgment
The draft is a starting point. You decide what leaves the room.
Selected repositories only. You choose which work contributes context.
Nothing posts automatically. Drafts stay available for review and editing.
Edit and copy anywhere. X Autopilot is coming soon, and you stay in control.
No pretend progress. Drafts stay grounded in the work your repository actually contains.
Start with your real GitHub work
Find one story worth sharing before you pay.
Start with a 14-day Builder trial. Connect the repositories you choose and see what Little Posts finds in the work you are already shipping.
14 days to find your first story Five distinct angles for every story Unlimited post generation on Builder
15.83
2 months free
190 billed yearly
19
Builder plan
Find my first storyThen $19 monthly or $190 yearly. Cancel anytime.