feat: git-cliff release notes via a reusable release-notes action#3
Merged
Conversation
- release-notes: composite action that installs git-cliff and renders release notes from the org-wide git-cliff config, written to a file for `gh release create --notes-file`. The git-cliff version and the config pin live in the action (both Renovate-bumped), so consumers just bump the action ref — no per-repo git-cliff wiring. - release.yml: dogfood ./release-notes instead of GitHub's auto-generated notes. - renovate.json: extend the org preset and bump the git-cliff-config pin in the action; REUSE.toml covers renovate.json (JSON has no comment syntax). - README: document the action. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Sebastian Hoß <seb@xn--ho-hia.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gh release create --notes-file. The git-cliff version and the config pin live in the action (both Renovate-bumped), so consumers just bump the action ref — no per-repo git-cliff wiring.