@commitlint/prompt
Advanced tools
commitizen adapter using commitlint.config.js
This is the library and commitizen adapter version of commitlint prompt. A ready-to-use cli version is available at @commitlint/prompt-cli. Learn how to use it at docs/prompt.
npm install --save @commitlint/prompt @commitlint/config-angular commitizen
echo "module.exports = {extends: ['@commitlint/config-angular']};" > commitlint.config.js
In package.json
{
"scripts": {
"commit": "git-cz"
},
"config": {
"commitizen": {
"path": "@commitlint/prompt"
}
}
}
git add .
npm run commit
5.0.0 (2017-11-18)
BREAKING CHANGE
TL;DR
Angular has removed the chore type from their conventions as of January 2017
See angular/angular@dff6ee for reference
This removes the previous chore type from the list of allowed types.
Projects using the Angular commit convention will identify commits with chore type as faulty.
Also, formerly working commit messages are now considered problems:
<a name="4.3.0"></a>
FAQs
commitizen prompt using commitlint.config.js
The npm package @commitlint/prompt receives a total of 80,814 weekly downloads. As such, @commitlint/prompt popularity was classified as popular.
We found that @commitlint/prompt demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.