The running doc of what you shipped, vs. a repo that already knows
A lot of indie makers keep a personal doc or spreadsheet: one row per week, a few bullets of what shipped. It works, right up until a busy week means the doc doesn't get updated and three weeks go un-logged.
Paste any public repo. Get this week’s post in seconds.
We read the repo’s last full week of public commits, PRs and issues. Nothing is stored, and there’s nothing to sign up for.
Side by side
| a spreadsheet or doc | Ship & Shout | |
|---|---|---|
| Setup | A doc or sheet you maintain yourself | Paste a repo, or connect it once |
| Keeping it current | Depends on remembering to open it | Reads the repo directly, every time |
| Source of truth | Your own notes | Commits, merged PRs, releases |
| Turning it into a post | Manual rewrite from your notes | Drafted for you, in your voice |
| Works if you skip a week | Gap stays in the doc | Picks up the next complete week automatically |
When the manual way still wins
- You're tracking things a repo can't see: user conversations, sales calls, decisions you made but didn't commit code for.
- You already have a doc habit that works for you — if it isn't broken, don't add a tool.
Questions
Can I use both — my own doc and Ship & Shout?
Yes. Plenty of makers keep personal notes for context (conversations, decisions) and let Ship & Shout handle the repo-side facts (commits, PRs, releases) so the doc doesn't have to cover everything.
Does it import my existing doc or spreadsheet?
No. It only reads GitHub activity (and revenue, if you connect Stripe or Lemon Squeezy). It doesn't read other documents or tools.
More comparisons
Get this every week, without pasting anything
Connect GitHub (read-only) and Ship & Shout drafts your week on the day you pick, with a revenue chart if you add Stripe or Lemon Squeezy. Nothing posts until you approve it.