We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
release-notes-generator uses conventionalcommits preset, but commit-analyzer doesn’t. This means changelogs and releases can end up out of sync.
For example, the following commit:
git commit -m 'feat!: do a major release'
…will generate a changelog like this:
### ⚠ BREAKING CHANGES * do a major release ### Features * do a major release
…but the commit-analyzer output is:
Analyzing commit: feat!: do a major release The commit should not trigger a release
The expected output is:
Analyzing commit: feat!: do a major release The release type for the commit is major
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
release-notes-generator uses conventionalcommits preset, but commit-analyzer doesn’t. This means changelogs and releases can end up out of sync.
For example, the following commit:
…will generate a changelog like this:
…but the commit-analyzer output is:
The expected output is:
The text was updated successfully, but these errors were encountered: