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
We should have the prompts ask if a breaking change is being committed. If true, then we should prepend the commit body with BREAKING CHANGE:.
true
BREAKING CHANGE:
For example:
feat(foo): Add new foo BREAKING CHANGE: API has now changed
Version of cz-github you're using: 1.0.5
cz-github
Node Version: 8.11
Operating System: macOS 10.13
The text was updated successfully, but these errors were encountered:
feat(flow): add new flow step
e6dd650
added a step to check if the commit is a breaking change and append it to the message Fixes ##11
4249677
chore(release): 2.0.0 [skip ci]
270d2c0
# [2.0.0](v1.0.5...v2.0.0) (2020-06-21) ### Bug Fixes * **validation:** change header max length to 72 ([c98d52d](c98d52d)) ### Build System * change minimum supported Node version ([d392e42](d392e42)) ### Features * **flow:** add new flow step ([4249677](4249677)), closes [#11](#11) ### BREAKING CHANGES * change minimum supported version of Node to v10
cainakleao
No branches or pull requests
Description
What is the use case that should be solved?
We should have the prompts ask if a breaking change is being committed. If
true
, then we should prepend the commit body withBREAKING CHANGE:
.For example:
Version of
cz-github
you're using: 1.0.5Node Version: 8.11
Operating System: macOS 10.13
The text was updated successfully, but these errors were encountered: