feat(meta 46): update CI to update CHANGELOG #4310
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update GitHub CI to automatically update CHANGELOG.md on main PR or main push using conventional-changelog-cli.
dosubot
bot
added
the
size:M
|
Coooool |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Important: this will require standardizing commit headers. See formatting notes here: https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular
Update Less.js GitHub CI with the capability to automatically update CHANGELOG.md on certain master pushes/PR merges.
Should resolve: less/less-meta#46
If a push or PR merge to master branch has a commit which has a header containing "Release v" the changelog CI will run and automatically commit changes to CHANGELOG.md.
Format:
On
masterpush:[commit header] ([commit hash])
On PR merge:
[commit header] ([PR link]) ([commit hash])
CHANGELOG.md sample:
Why:
Currently CHANGELOG.md maintenance is a manual effort which takes time and can be error prone.
Checklist:
Should preserve historical CHANGELOG.md contents created via different means.
We can tweak the change formatting by adding a new configuration file, I went with the default
angularstyle that did not require adding a configuration file.