feat: Add commits to Unreleased when no tags. #186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do / why do we need it?
When there are commits and no existing git tags, add any notable changes to the "Unreleased" section of the change log.
This requires is a breaking change because
git-chglog --init
Existing template will still work.
How this PR fixes the problem?
In the
chglog.go
file some function have been update so that if the code cannot find any tag and there is no value set for "nexttag" or in the query, then allow a CHANGLOG.md to get generated. The template has been updated to alllow the "Unreleased" section to be displayed even when no previous versions exist.Changed the code in several places so that when there is no tag query set, then continue program execution, even if no tags are found. Thus removing the "no tags" error, if any programs parsed that error they will break. This allows unreleased commits from the beginning of he repositories history to be collected.
In addition, the templates had to be modified to allow adding the unreleased sections independent of versions. Since there will be no versions, as implied when there are no tags.
What should your reviewer look out for in this PR?
Check lists
Additional Comments (if any)
Again, I am proposing this BREAKING CHANGE, which is that the program will never show the no tags error message again. The closes a PR that changes that message.
Which issue(s) does this PR fix?
fixes #76
closes #187