CTCaer/switch-l4t-atf
1
0
Fork 0
mirror of https://github.com/CTCaer/switch-l4t-atf.git synced 2025-01-05 17:49:13 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
fea7f36938
switch-l4t-atf/package.json

14 lines
282 B
JSON
Raw Normal View History

build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
{
"private": true,
"scripts": {
"postinstall": "husky install"
},
"devDependencies": {
build(hooks): add commitlint hook This change adds a configuration for commitlint - a tool designed to enforce a particular commit message style - and run it as part of Git's commit-msg hook. This validates commits immediately after the editor has been exited, and the configuration is derived from the configuration we provide to Commitizen. While the configuration provided suggests a maximum header and body length, neither of these are hard errors. This is to accommodate the occasional commit where it may be difficult or impossible to comply with the length requirements (for example, with a particularly long scope, or a long URL in the message body). Change-Id: Ib5e90472fd1f1da9c2bff47703c9682232ee5679 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 16:52:03 +00:00
"@commitlint/cli": "^11.0.0",
"@commitlint/config-conventional": "^11.0.0",
build(hooks): update Commitizen to ^4.2.4 An indirect dependency of Commitizen (`merge`) is currently failing the NPM.js auditor due to vulnerability CVE-2020-28499. This commit moves the minimum version of Commitizen to 4.2.4, which has resolved this vulnerability. Change-Id: Ia9455bdbe02f7406c1a106f173c4095943a201ed Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-05-12 14:22:42 +00:00
"commitizen": "^4.2.4",
build(hooks): add Commitizen hook This change adds Commitizen, an interactive tool for writing commit messages, to the package.json file. This installs Commitizen within the `node_modules` directory automatically when developers invoke `npm install` from the root repository directory. Additionally, this change adds a prepare-commit-msg Git hook which invokes Commitizen prior to generation of the default commit message. It may be exited with the standard ^C signal without terminating the commit process for those who desperately want to avoid using it, but otherwise should encourage developers to conform to the new commit style without running into post-commit linting errors. Change-Id: I8a1e268ed40b61af38519d13d62b116fce76a494 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 14:35:46 +00:00
"cz-conventional-changelog": "^3.3.0",
build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
"husky": "^5.0.4"
}
}
Reference in New Issue Copy Permalink