You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: clarify allow-no-commit changelog behavior and docs
Align internal typing/forwarding for allow_no_commit, simplify the regression test setup, and document how changelog entries are generated during no-commit bumps.
Made-with: Cursor
When `update_changelog_on_bump = true` (or `--changelog` is used), `cz bump --allow-no-commit` also generates a changelog entry even if there are no commits in the selected range.
478
+
479
+
This makes the new release visible in the changelog while still showing that no commit-based changes were included.
480
+
476
481
### `--tag-format`
477
482
478
483
`tag_format` and [version_scheme][version_scheme] are combined to make Git tag names from versions.
Copy file name to clipboardExpand all lines: docs/commands/changelog.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
3
3
Generates a changelog following the committing rules established.
4
4
5
+
When changelog generation is triggered by `cz bump --allow-no-commit` (with `--changelog` or `update_changelog_on_bump = true`), Commitizen still creates a release entry even when no commits are found in the selected revision range.
6
+
5
7
!!! tip
6
8
To create the changelog automatically on bump, add the setting [update_changelog_on_bump](../config/bump.md#update_changelog_on_bump)
0 commit comments