I tag releases, then dread writing the notes. So I automated it.

Description and use

An offline, one‑command tool that auto‑generates release notes from Conventional Commit logs, outputting Markdown or JSON.

Problem

After tagging a release, manually compiling release notes from commit logs is tedious and error‑prone.

Outcome

The script produces categorized release notes (Breaking Changes, Features, Fixes, Other changes) in Markdown, reducing manual effort and minimizing missed changes.

Workflow

• 1. Download script: curl -O https://raw.githubusercontent.com/hahahahahahahahah6/git-release-notes/main/git_release_notes.py
• 2. Make executable: chmod +x git_release_notes.py
• 3. Run script: ./git_release_notes.py
• 4. Capture output (Markdown) and copy to release page or pipe to pbcopy.
• 5. Optional flags: --verbose, --json, --title v1.4.0.
• 6. Script diffs from most recent tag reachable from HEAD; if empty, falls back to previous tag.

Evidence

git-release-notes does that archaeology for you — in one command, offline, conventional-commit aware:

Source

With no arguments it diffs from the most recent tag reachable from HEAD to HEAD (and if the range is empty only because you just tagged, it falls back to the previous tag instead).

Source

This is not a GitHub-Action release drafter. No API, no tokens, no CI workflow to wire up — it works on a plane, in a monorepo, on a bare server.

Source