Changelog Generator

Ship a changelog your users actually read.

Generate CHANGELOG.md in Keep-a-Changelog format. Drop in git commits and we'll classify them by type.

Keep a Changelog 1.1SemVer-readyGit log import

Project info

Used to link version tags to GitHub releases

Import from git log

Paste output of: git log --oneline. We auto-classify Conventional Commits (feat → Added, fix → Fixed, etc).

Releases · 1

v1.0.0

CHANGELOG.mdmarkdown
# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.0] - 2026-04-29

Want changelogs that publish themselves?

Dokly auto-generates a changelog page from your release notes — with RSS, search, and version filters.

Try Dokly free →

What is Keep a Changelog?

Keep a Changelog is the de facto standard for maintainable software changelogs. Every release gets a version, a date, and a structured list of changes grouped under six categories: Added, Changed, Deprecated, Removed, Fixed, Security.

Why a structured changelog matters

  • Users notice: a clean changelog is the cheapest customer-comms surface you have.
  • Semver discipline: grouping by type forces you to think about breaking vs additive vs patch.
  • GitHub release notes: a well-formed CHANGELOG drops straight into release tags.

Conventional Commits → changelog

If you write commits like feat: add dark mode and fix: handle null user, the “Import from git log” box auto-classifies them. Paste git log --oneline v1.0.0..HEAD and your release entries appear, sorted into the right buckets.