-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Add git-cliff support for changelog generation #1825
Conversation
Check for feat tag Check for build tag Better quotes Check for all our conventional commits Officially recognise build section in changelog Update docs for conventional commits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
See also #1834. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of minor comments, but looks good to me - I'm a big fan of Conventional Commits.
@trisyoungs That is a very valid question. My updated
|
Co-authored-by: Jared Swift <[email protected]>
Co-authored-by: Jared Swift <[email protected]>
r) BRANCH=$(git rev-parse --abbrev-ref HEAD) | ||
if [ "$BRANCH" != "Release" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this right? If I run this on a release branch I get, for example, release/1.4.3
which wouldn't satisfy the test...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm specifically creating a branch named Release
, since release
was already taken. It is only on that branch that the test will pass.
DO NOT MERGE WITHOUT WARNING THE REST OF THE TEAM
This PR adds a check to the CI that will enforce the use of Conventional Commits when submitting a PR. A pull request template is included to remind developers to include an appropriate title for their PR.
As a final change, the
changeversion
script is updated to automatically pull the next version number fromgit cliff --bump
. This also means that it is no longer necessary (or possible) to pass the desired version type to the script.