fix(ci): pass tag range to git-cliff so release body covers current release only #74
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sarman/tftsr-devops_investigation#74
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/changelog-range-scope"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
git-cliff's --tag flag sets a version label, it does not restrict which
commits are scanned. Without a positional range argument, git-cliff walks
the entire commit history and generates every historical release section,
producing a release body that contains the full changelog.
Pass "${PREV_TAG}..${CURRENT_TAG}" as the range argument so git-cliff only
processes commits introduced in the current release. The full CHANGELOG.md
generation is unchanged (no range — intentional, it covers all tags).
git-cliff's --tag flag sets a version label, it does not restrict which commits are scanned. Without a positional range argument, git-cliff walks the entire commit history and generates every historical release section, producing a release body that contains the full changelog. Pass "${PREV_TAG}..${CURRENT_TAG}" as the range argument so git-cliff only processes commits introduced in the current release. The full CHANGELOG.md generation is unchanged (no range — intentional, it covers all tags).Pull request closed