[DEV] Automate CHANGELOG.md creation using git-chglog #45
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.
This PR…
closes #36
Todo
Considerations and implementations
For a commit to appear in the CHANGELOG.md, it has to follow a certain naming pattern:
[type] ...(#PR-number)
possible types:
example:
[FEATURE] Add check for required input parameter for CLI and GUI (#41)
After installing git-chglog locally, the CHANGELOG.md can be generated with this command:
git-chglog -o CHANGELOG.md
To generate the CHANGELOG for a upcoming release (no tag exists yet), the following command can be used:
git-chglog -o CHANGELOG.md --next-tag v0.10.0
The already existing CHANGELOG entries were copied to the template so that they get included in the generated CHANGELOG.md even if the commits are not following the naming pattern.
How to test
see upper chapter
Optional
Unit-Test(s) added
Having this section helps reminds developers to always add tests, or explain themselves if they can’t!
Screenshots
Having this section makes visual changes immediately obvious, and means visual bugs can often be identified instantly. Also, the screenshots are useful for non-devs preparing content for sprint review, or signing off work.
It’s worth mentioning that in less visual projects, this section could be called “Changes” and contain logs / process flows / etc. This section sometimes contains screenshots of Charles network requests or LogCat messages as well as normal screenshots.