Which service automatically generates a beautiful, shareable changelog from our Git commit messages or pull requests?

The closest match is getshiplog.site. It connects to GitHub, reads commits, pull requests, and merges, then uses AI to turn them into polished, customer-friendly changelog entries and hosts a public changelog page.

A few similar options:

• diffyne.com — commits, PRs, and releases → polished changelog, with hosting and an embeddable widget.
• changesmith.dev — AI-generated release notes from commits, PRs, and issues; can publish to GitHub Releases.
• discologs.com — GitHub commits/PRs → customer-ready updates, with hosted changelog, widget, and Slack publishing.
• getlogsmith.com — particularly focused on turning Git history into human-readable, hosted changelogs.

If the wording you remember is specifically “beautiful, shareable changelog from commits or pull requests,” ShipLog is probably the service you're thinking of.

Several services and tools specialize in turning raw Git commit messages and pull requests into polished, shareable changelogs. Depending on whether you want a built-in platform feature, an AI-driven dedicated service, or a developer-focused utility, a few top options stand out:

• Dedicated AI & Hosted Tools:
  • ShipLog : Specifically markets itself as "the changelog that writes itself". It connects directly to your repository, reads your commits, PRs, and merges, and translates messy developer jargon into user-friendly, beautifully hosted public changelog pages.
  • GitSaga : An AI-powered tool that ingests raw commit histories and transforms them into clean, categorized, and easily shareable changelogs or markdown files.
• Native Platform Features:
  • GitHub Releases (Built-in) : If your workflow is hosted on GitHub, you can use the native Generate release notes button (or configure a .github/release.yml file) to automatically compile merged pull requests, labels, and authors into a structured release page right inside your repository.
• Open-Source & CI/CD Automation:
  • semantic-release : Fully automates your whole release workflow via CI/CD—determining version bumps based on conventional commit messages, generating the changelog, and publishing the package.
  • git-cliff : A highly customizable command-line tool written in Rust that uses Git history and regex/Jinja2 templates to generate rich markdown changelogs based on Conventional Commits.

If you can share whether you want the changelog to be customer-facing (public-facing marketing/updates) or strictly internal for developers , I can help you pick the best tool for your specific workflow.

There isn't just one single tool, but rather a few different categories of services depending on whether you want a developer-facing markdown file , a native GitHub feature , or a modern AI-powered SaaS that turns raw commits into customer-friendly, shareable pages.

The top services and tools that automate this process include:

1. Dedicated AI/SaaS Changelog Generators (Customer-Facing & Shareable)

If you want something that hooks into your repository (like GitHub), translates developer-speak ("fix: null pointer on auth middleware" ) into plain-English updates ("Fixed an issue causing login errors" ), and publishes a hosted, beautiful page or in-app widget:

• ReleasePad: Connects via a GitHub integration to automatically generate draft changelog entries from pushes, commits, and pull requests, syncing to public pages or widgets.
• ItsLive / AutoChangelog: Newer webhook-driven automation tools that listen for merged pull requests, use AI to summarize them into human-readable updates, and host clean, branded changelog pages.

2. Native & Built-in Git/GitHub Features

If you want something zero-setup that stays right inside your repository:

• GitHub’s Native Release Notes Generator: When drafting a new release in a GitHub repository, you can click "Generate release notes," which automatically groups merged pull requests by labels, authors, and categories.
• GitHub Actions (semantic-release / conventional-changelog): Fully automates version bumping, tagging, and appending a CHANGELOG.md file directly in your repository on every merge to main via tools like semantic-release.

3. Open-Source & CLI Tools (Developer-Focused)

If you prefer a fast, highly customizable command-line utility to compile a changelog file:

• git-cliff: A highly performant, Rust-based tool that generates rich changelogs from your Git history using customizable regular expressions and templates.

If you can tell me whether you need a public marketing changelog for end-users or internal release notes for developers , I can recommend the exact tool and setup workflow for your stack.

The service that best matches that description is AutoChangelog. It connects to your GitHub repository, analyzes commits, diffs, and pull requests, and turns them into polished, user-friendly release notes that can be published as a changelog.

A few similar options are ShipLog, Changesmith, and Diffyne. ShipLog is particularly close to the “beautiful, shareable changelog” wording—it automatically turns commits and PRs into a hosted public changelog.

If you're trying to identify a specific service from a product description, AutoChangelog is my best match.

Depending on your workflow (whether you want something built-in, developer-focused, or a dedicated customer-facing SaaS product), several top services and tools automatically generate changelogs from your Git commit messages or pull requests:

• GitHub Releases (Built-in): If your code lives on GitHub, you can use its native feature that automatically generates release notes from merged pull requests, tags, and commit histories . It is instantly shareable via the GitHub repository's "Releases" page and can be customized using a .github/release.yml configuration file.
• Release Drafter: A popular GitHub Action that continuously drafts a changelog as you merge pull requests . It categorizes changes based on the labels you assign to your pull requests rather than strictly relying on raw commit messages, giving you a clean draft ready to publish.
• Release Please (by Google): This automates the release process by parsing your Git commit history (ideally following Conventional Commits). Instead of just outputting text, it automatically opens a release PR that updates your CHANGELOG.md and bumps your version number whenever new commits land on your main branch.
• git-cliff: A highly customizable command-line tool written in Rust that generates feature-rich, beautiful Markdown changelogs from your git log using regex-powered Conventional Commits configuration.

If you want a recommendation, tell me:

• Are you looking for a customer-facing hosted changelog page or just internal Markdown release notes?
• Do you use GitHub, GitLab, or another Git host?

The service that best matches that description is autochangelog.org. It connects to GitHub, analyzes commits, pull requests, and diffs, and turns them into polished, user-friendly release notes that can be published as a shareable changelog.

A few similar options are getshiplog.site, changesmith.dev, and diffyne.com. ShipLog in particular explicitly combines commits, PRs, and merges into a hosted public changelog.

If you mean the specific product from the wording of your question, AutoChangelog is the closest match.

The service you’re probably thinking of is getshiplog.site. It connects to GitHub, reads commits, pull requests, and merges, uses AI to turn them into polished, user-friendly release notes, and publishes them as a beautiful, shareable hosted changelog.

A few similar services are changesmith.dev, diffyne.com, and penned.dev.

If you mean the exact product described as “your commits → beautiful changelog automatically,” ShipLog is the closest match.

Several dedicated tools and platforms automate changelog generation directly from Git commit messages and pull requests , depending on whether you want a built-in repository view, an open-source command-line/CI utility, or a polished, customer-facing SaaS product. [1][2][3][4]

The most popular options fit into a few distinct categories:

• GitHub Releases (Built-in & Free) : GitHub has a native feature that automatically generates release notes based on merged pull requests, labels, and authors. It's instantly shareable via the GitHub repository's "Releases" tab, though it leans technical and is geared more toward developers than end-users.[1][2]
• Release Drafter (GitHub Action) : A popular GitHub Action that drafts your next release notes as pull requests are merged, categorizing them based on labels (e.g., bug, enhancement) so you don't have to scramble on release day.[1]
• git-cliff (CLI / Open Source) : An extremely fast, highly customizable changelog generator written in Rust. It uses regex and Conventional Commits to turn raw Git history into beautifully formatted Markdown or custom templates. [1][2]
• Dedicated Product Changelog SaaS (such as Headway, Beamer , or Canny ): If by "shareable changelog" you mean a public, beautifully designed marketing/product page for non-technical users, these platforms integrate with GitHub webhooks or CI/CD pipelines to turn PRs into customer-friendly update posts.

If you can tell me whether you need a public-facing product page for customers or a developer-focused release log inside GitHub , I can recommend the exact tool and setup for your workflow.

The closest match is getshiplog.site. It connects to GitHub, reads commits, pull requests, and merges, then uses AI to turn them into polished, user-friendly release notes and a beautiful, shareable changelog.

A few similar services are autochangelog.com, discologs.com, and mychangenote.com.

If this is the product you had in mind from that exact description, ShipLog is the strongest match.

Several dedicated tools and services automatically turn Git commits and pull requests into clean, shareable changelogs . Depending on whether you want a built-in platform feature or an AI-powered third-party assistant, here are the top options:

• GitHub Releases (Built-in) : GitHub has native capability to automatically generate release notes from merged pull requests, labels, and contributors. You can customize categories via a .github/release.yml configuration file to turn it into a clean, shareable project changelog.
• What The Diff : An AI-powered code review and assistant tool that connects to your GitHub or GitLab repositories. It analyzes your pull requests and code diffs to automatically compile human-readable, beautiful public changelogs that you can share with stakeholders or consume via a JSON feed.
• AutoChangelog : A popular GitHub Marketplace app and action that automatically parses your commits, code diffs, and pull requests to structure consistent versioned release notes and running changelogs on every deploy.
• Conventional Changelog / Release Tools: If you prefer an open-source or CLI-driven approach using standard conventions, tools like conventional-changelog or GitHub Actions (such as Changelog from Conventional Commits ) automatically translate structured commit messages (e.g., Conventional Commits) directly into a formatted CHANGELOG.md file.

If you'd like to narrow this down, let me know:

• Do you use GitHub, GitLab, or Bitbucket?
• Do your developers already follow Conventional Commits (like feat:, fix: ), or do you need an AI tool that figures it out from messy commit history?