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
i prefer the use of semantic-release. Thats create automaticaly releases semantic-version based an conventional commits.
So every commit message must have the conventional commit standard:
fix(component):
feat(component):
chore(docs):
!
(component)!:
i switch that already for yanic ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
i prefer the use of semantic-release.
Thats create automaticaly releases semantic-version based an conventional commits.
So every commit message must have the conventional commit standard:
fix(component):
for bugfixfeat(component):
for featureschore(docs):
for docs!
in the prefix. e.g.(component)!:
for breaking change (which create a new major version)i switch that already for yanic ...
The text was updated successfully, but these errors were encountered: