Fail release if no CHANGELOG additions have been made
#192
Labels
Comments
TheAngryByrd
pushed a commit
that referenced
this issue
Feb 24, 2020
TheAngryByrd
pushed a commit
that referenced
this issue
Feb 24, 2020
TheAngryByrd
pushed a commit
that referenced
this issue
Feb 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Currently if you don't use the correct CHANGELOG format with ``### changed` headers (or others) it will wipe out what you wrote and just release an empty release. See example. We should fail if there are no notes in any of the sections.
To Reproduce
##[unreleased]section with notes not associated with a header./build.sh Release newVersionExpected behavior
Fail if there are no changes in the changelog
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
The text was updated successfully, but these errors were encountered: