cz-cli
cz-cli copied to clipboard
commitizen
The commitizen command line utility. #BlackLivesMatter
Expected behavior: ``` git cz -m "somemessage" ``` expected: results in prefilled `somemessage` actual: results in prefilled `Write a short, imperative tense description of the change:`
In my setup, the git repository is placed in `/home/user/Code/namespace/prj-name/`, but all the CI/CD code is placed in `/home/user/Code/namespace/prj-name/cx` (in part, because it is not a JS project, and I...
When I scroll all the way down to `revert`, it cycles down to `feat`. I can't easily figure out if I've exhausted all the options This is from the perspective...
Hi, Thanks for your nice tool, that's very handy. It would be awesome to have scope propostions from previous scopes from the commit history. Because it's hard to remember what...
Why not allow usage without prompts: `git-cz --type feat --scope some --desc "commit message"`
Lower maintenance burden (and adopters' impressions of projects) by auto-merging minor dependency upgrades OR ignore all but major version updates for dependencies. Pin all dependencies to avoid insecure updates for...
Currently when writing a prompter, e.g., cz-conventional-commit, if you wish to integrate with commitizen configuration then you need to do the following: ``` var configLoader = require('commitizen').configLoader; configLoader.load() // synchronous,...
Currently if I try to create a commit with breaking changes but without a longer description I get the following message: "A BREAKING CHANGE commit requires a body. Please enter...
Metadata
Owner
Metadata
The commitizen command line utility. #BlackLivesMatter