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
git clone https://github.com/git-chglog/git-chglog.git
# git commit --amend# add a footer note: # BREAKING CHANGE: big breaking change!
git-chglog -o CHANGELOG.md
git diff
# you'll then see that no breaking change section is added.
Your Environment
OS: OSX Big Sur
git-chglog version: 0.14.2
The text was updated successfully, but these errors were encountered:
It looks like what is happening is that when the change set is a part of the Unreleased category, the BREAKING CHANGE is not caught. You can test his by running the same repro case with the --next-tag <ANYTHING> set. This will inject a pseudo tag and result in the BREAKING CHANGE to be noted as expected.
I have been wanting to find time to refactor how the Unreleased and next-tag features are handled within the tool. There are some tricky cases to handle, but it would be nice if the behavior was consistent across all "tags" regardless if they are real, pseudo or unreleased.
Expected Behavior
BREAKING CHANGE
section added to CHANGELOGActual Behavior
BREAKING CHANGE
section not added to CHANGELOGSteps to Reproduce (including precondition)
Your Environment
The text was updated successfully, but these errors were encountered: