Repository navigation
chore: add changelog generation workflow and initial changelog files - #12
Merged
Merged
Conversation
Awesome-Ace22
added
documentation
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
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.
This pull request introduces automated changelog generation for the repository using git-cliff and GitHub Actions. It adds configuration and documentation to ensure changelogs are consistently built from PR titles and managed through PRs into the
devbranch. The most important changes are:Changelog automation infrastructure:
.github/workflows/changelog.ymlworkflow to automatically generateCHANGELOG.mdusing git-cliff when changes are pushed tomainor triggered manually, and open a PR intodevwith the updated changelog.cliff.tomlconfiguration file specifying how git-cliff should format and group changelog entries, enforcing Conventional Commits and Nova release tagging.Documentation:
CHANGELOG.mdfile with instructions and a note that it is managed by the changelog workflow and should not be edited by hand.