Sign in
Start free trial
Sign in
Free tool · changelog

Turn last week's commits into a changelog people will read

Raw commit logs are full of "fix typo" and "wip". This reads a public repo's last full week of commits, merged PRs and releases, groups them into the handful of changes that matter, and writes them as plain-language bullets. Hit "Copy as changelog" for a Markdown entry you can paste straight into CHANGELOG.md or your release notes. If last week was quiet, it uses the repo's most recent active week instead.

TRY IT · NO ACCOUNT NEEDED

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.

or try
Your sample post appears here
Written in a no-hype voice, with real numbers from the repo.

What you get

Sample changelog entry (illustrative)
## Week of Sep 26 – Oct 2, 2026

Released: v15.5.1, v15.5.2

### Added
- Kept ISR cache lifetimes across restarts

### Fixed
- Broken pnpm builds in Docker examples

### Improved
- Faster cold starts for image routes

What goes into the changelog

  • Commits on the default branch from the last complete week (Saturday to Friday, UTC).
  • Merged pull requests and their titles, which usually describe changes better than commit messages.
  • Tagged releases in that window, so a version bump shows up as a release, not just a commit.
  • Closed issues are counted too, so bug-fix weeks get credit.

How to get a better changelog from your commits

  • Write PR titles as outcomes ("Exports open in Excel"), not tasks ("update csv writer").
  • Squash-merge feature branches so one feature becomes one entry.
  • Tag releases when you ship. Tagged versions get called out separately.
  • Keep chores in their own PRs so they're easy to filter out.

Highlights, not a commit dump

The writer picks the few changes worth mentioning from PR titles and commit messages and leaves routine work in the totals. It's a draft: edit, reorder or cut anything before you use it.

From weekly changelog to weekly post

A changelog tells users what changed. A build-in-public post tells your audience why it matters. Ship & Shout writes both from the same data: the shipped list here, plus a short post in your voice, with an optional revenue chart from Stripe or Lemon Squeezy once you sign up.

Questions

Does it work with private repositories?

The free tool reads public repos only, using GitHub's public API. Private repos work after you sign up and install the read-only Ship & Shout GitHub App on the repos you choose.

Which time window does the changelog cover?

The last complete week, Saturday to Friday in UTC. The week in progress is skipped so the changelog never covers half a week.

Is my code or repo data stored?

No. The tool reads commit metadata (messages, PR titles, release tags), never file contents, and stores nothing about the repo or you. Results are cached in memory for an hour so a popular repo isn't fetched twice.

Can I get this every week automatically?

Yes, two ways. For the changelog file itself, add the free Weekly Changelog GitHub Action: it opens a PR every Monday that adds the week's entry to CHANGELOG.md. For posts, sign up and connect GitHub, and Ship & Shout drafts the week on the day you pick. Nothing is posted until you approve it.

More free tools

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.