
ShipLog
Your PRs write your changelog. Automatically.
21 followers
Your PRs write your changelog. Automatically.
21 followers
ShipLog connects your GitHub repo to generate beautiful, user-facing changelogs from your merged PRs. It automates the changelog creation process, allowing you to focus on shipping features rather than writing release notes. With ShipLog, you can publish updates across multiple channels, ensuring your users are always informed about the latest changes. The tool offers features like, weekly email digests for re-engagement, and integration with various platforms to enhance visibility and retention






Free Options
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startupās next milestone
Promoted

I like the āPRs ā user-facing changelogā direction. The hard part is usually not generating release notes, itās deciding which engineering changes deserve customer-visible framing and which audience they matter to.
A feature Iād look for: a review step that labels each merged PR as user-visible / internal / bugfix / infrastructure, then drafts the update in benefit language instead of implementation language. That would make it much easier for small teams to turn shipping cadence into retention without creating noisy changelogs.
@jim_jeffersĀ yeah exactly ... that filtering layer is honestly the harder problem than generation itself
otherwise every changelog just becomes engineering noise š
weāve been thinking a lot about:
āis this user-visible?ā
āwho actually cares about this update?ā
āhow do we frame this as value instead of implementation?ā
really good insight, appreciate this
@mrcybernaut That āengineering noiseā line is the whole product problem. If you have one merged PR that produced a too-implementation-heavy changelog draft, Iād be happy to do a quick gut check: what should become user-visible value vs stay internal. One bullet/paragraph is enough.
@jim_jeffersĀ hey Jim, that's a great suggestion and we already have this implemented. Right now we are already ignoring/filtering out those pull requests which change internal files and are not adding anything meaningful to the product.
So only those pull requests which have meaningful change contribute to changelogs. In those changelogs also we have categories like Improvements, Fixes, Bugs..etc.
And before publishing user can always edit a changelog or change it's category, it's stored as a draft at first.