Skip to content

Fix empty commit links in CLI release notes - #36

Merged
yosriady merged 2 commits into
mainfrom
codex/fix-release-note-script-for-cli
Aug 3, 2026
Merged

Fix empty commit links in CLI release notes#36
yosriady merged 2 commits into
mainfrom
codex/fix-release-note-script-for-cli

Conversation

@yosriady

@yosriady yosriady commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Motivation

  • Release notes were rendering empty commit links (shown as ()) because the git log output used spaces as a delimiter while the parser expects a tab-separated subject and hash.

Description

  • Use a real tab delimiter in git log by switching to --pretty=format:'%s%x09%h' so the loop parsing with IFS=$'\t' receives both subject and hash.
  • Quote the previous-tag revision range ("${PREV_TAG}..HEAD") passed to git log to avoid shell word-splitting issues.
  • Add an inline comment documenting why the delimiter must remain aligned with the release-note loop.

Testing

  • Ran git diff --check which produced no whitespace or formatting errors.
  • Validated the release-note generation by iterating git log output with IFS=$'\t' read -r message hash and asserting every hash was non-empty and no entry contained an empty () link, confirming generation for repository history (37 entries) succeeded.
  • Confirmed the workflow file change is present and the delimiter regression check shows the parsed message and hash are both non-empty.

Codex Task


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@yosriady
yosriady merged commit ceeff7e into main Aug 3, 2026
7 checks passed
@yosriady
yosriady deleted the codex/fix-release-note-script-for-cli branch August 3, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant