Open
Description
Description
It would be nice to get for each commit in the generated changelog as as optional variables:
- short commit SHAs, linked to the commit in github
- issue number, linked to the issue in github
See an example that was generated with conventional-changelog-cli (node.js). See npm script that generates the changelog.
The justification is that having short commit hash and issue number as clickable links in repo gives a possibility to quickly access the related code and issues/threads in github, thus having full context of the item / entity worked on, without having to search for it by hand, that would take much more time.

Possible Solution
add linked commit hash and issue number as optional variables to each commit to changelog format
Additional context
No response
Additional context
No response
Activity
kmnhan commentedon Oct 8, 2024
As a workaround, I built a plugin that tries to do what is mentioned. It will be great to have this implemented natively!
woile commentedon Oct 8, 2024
Wanna add it to the third party section in the docs?
https://commitizen-tools.github.io/commitizen/third-party-commitizen/
kapsner commentedon Jun 2, 2025
@nongrata081 I got this working by modifying the template as follows:
Adding
({{ change.sha1[:7] }})
includes the commit hash behind the change-message.Changelog is updated with
cz ch --template _templates/CHANGELOG.md.j2
.When pushing the CHANGELOG.md to GitHub/GitLab, the hash is automatically linked to the respective commit; same is ensured when referencing issue numbers or even contributors in the change messages.