codeaholicguy Changelog
Update the top Unreleased list in CHANGELOG.md from commits after the latest release.
Workflow
- Find the latest release base:
- Prefer the latest reachable tag:
git describe --tags --abbrev=0. - If there are no tags, search recent history for a release commit and use that hash.
- Prefer the latest reachable tag:
- Get commits:
git log <base>..HEAD --reverse --format='%H%x09%s'. - Derive the GitHub repo URL from
git remote get-url origin. - For each commit, add one concise changelog line:
- Format:
- [<short-hash>](<url>) <one-line summary> - If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
- Detect PRs from subjects like
(#123), merge commits, orgh pr list --search <hash> --state all --json number,url.
- Format:
- Insert the new lines into the top
Unreleasedsection/list inCHANGELOG.md.- If no
Unreleasedsection exists, create one at the top. - Do not create a dated release heading unless the user asks for a release.
- If no
Rules
- Keep one line per commit.
- Preserve the existing changelog style when obvious.
- Always add entries to the top
Unreleasedlist. - Skip noisy commits only when clearly non-user-facing and explain what was skipped.
- Do not invent PR links; use commit links when PR evidence is missing.