I would like to propose the addition of a new workflow named "Changelog" to automate the generation of a conventional changelog on the main branch whenever code changes are pushed.
The Changelog workflow should be triggered automatically on every push to the main branch.
The workflow should utilize the TriPSs/conventional-changelog-action@v3 and actions/create-release@v1 actions as specified in the workflow YAML.
When the workflow runs, it should generate a conventional changelog and create a new release on GitHub if there are any changes.
The release name and tag should be identical and derived from the generated changelog.
The conventional changelog should be used as the release body.
I am looking forward to having this automated Changelog workflow in place to streamline our development process and improve transparency with clear and concise changelogs for each release.
Description
main
branch whenever code changes are pushed.Screenshots