Changelog Generator

Generate formatted CHANGELOG.md files from git commit logs with version categorization.

Parsed 0 Conventional Commits

About Changelog Generator — Detailed Guide

The Changelog Generator parses raw Git commit logs and formats them into standardized, release-ready `CHANGELOG.md` documentation. It understands Conventional Commits syntax as well as standard commit messages.

Commits are grouped into structured categories: Features, Bug Fixes, Performance Improvements, Documentation, and Refactoring. Configure release version tags and dates, filtering merge commits for one-click Markdown export.

#changelog #git #release #version #history

Key Features & Capabilities

  • Directly parses output from native `git log --oneline` terminal commands
  • Classifies commit entries automatically by Conventional Commit types (feat, fix, perf, docs)
  • Configurable release version tag and date banners adhering to Keep a Changelog standards
  • Filters out noisy merge commits and outputs clean, copy-pasteable Markdown

How to Use

  1. 1

    Run `git log --oneline` in your repository terminal and paste the logs into the input field.

  2. 2

    Enter your target release version (e.g. `v1.2.0`) and choose a release date.

  3. 3

    Review the categorized release notes and click Copy or download `CHANGELOG.md`.

Common Use Cases

  • → Assembling release notes for GitHub Releases before deploying production updates
  • → Maintaining a centralized, historical CHANGELOG.md file for open-source repositories
  • → Translating dense technical commits into readable changelogs for product stakeholders

Related Tools

Frequently Asked Questions & Privacy

How can I extract commits since the last release tag?

Run `git log <previous-tag>..HEAD --oneline` in your terminal to isolate commits made strictly after the previous release.

How are non-conventional commits classified?

Commits lacking conventional prefixes are grouped under an "Other Changes" section, ensuring no commit information is missed.