-
-
Notifications
You must be signed in to change notification settings - Fork 301
feat(changelog): add support for multiline BREAKING paragraph #348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2579c3b
to
f0fdb6d
Compare
Codecov Report
@@ Coverage Diff @@ ## master #348 +/- ## ======================================= Coverage 97.29% 97.29% ======================================= Files 35 35 Lines 999 999 ======================================= Hits 972 972 Misses 27 27
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
I'm aware I'm introducing a side-effect which I think is cool.
Given this commit message:
fix: user module now work
fix: another fix
BREAKING CHANGE: You have to fix `here` and `there`
footer
Would output this CHANGELOG:
### Fix
- user module now work
- another fix
### BREAKING CHANGE
- You have to fix `here` and `there`
f0fdb6d
to
f9ac355
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor suggestion. Other than that everything looks good to me 🙂
f9ac355
to
0621bc4
Compare
Uh oh!
There was an error while loading. Please reload this page.
Description
Checklist
./script/format
and./script/test
locally to ensure this change passes linter check and testExpected behavior
Support for multiline body, suppose a commit message like this:
Commitizen will detect a
fix
and aBREAKING CHANGE
both will be added to the changelog
Steps to Test This Pull Request
cz changelog
cat CHANGELOG.md
Additional context
Closes #346