arm-trusted-firmware/.cz.json

{
    "path": "@commitlint/cz-commitlint"
}
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> 4 years ago			`{`
refactor(hooks): replace cz-conventional-changelog with cz-commitlint This change replaces cz-conventional-changelog with cz-commitlint, which automatically configures Commitizen using our commitlint configuration file. Currently, we use some manual Javascript magic to load our Commitizen configuration into commitlint (the opposite of what's introduced by this change), which can be removed. With this change, we also move our commitlint configuration into a new `changelog.yaml` file. This file holds the same data as `.cz.json` previously did. Change-Id: I14ff2308f1a0b2b293c2128b28ca2df578ce9c1c Signed-off-by: Chris Kay <chris.kay@arm.com> 3 years ago			`"path": "@commitlint/cz-commitlint"`
build(docs): introduce release script This change introduces a new NPM run script to automatically generate the release changelog, as well as bump version numbers across the code-base and create the release tag. This script runs [Standard Version] to execute this, which is a tool designed around automating substantial parts of the release process. This can be done by running: npm run release -- [<standard-version args>] Standard Version expects the project to adhere to the [Semantic Versioning] convention which TF-A does not, so you may need to specify the version manually, e.g.: npm run release -- --release-as 2.6.0 Individual steps of the release process may also be skipped at-will, which may be necessary when, for example, tweaking the changelog: npm run release -- --skip.commit --skip.tag Standard Version is configured by the `.versionrc.js` file, which contains information about the Conventional Commits types and scopes used by the project, and how they map to the changelog. To maintain continuity with the existing changelog style - at least to the extent possible in the move from manual to automatic creation - a customized changelog template has been introduced, based on the Conventional Commits template provided by Standard Version. This template package extends the Conventional Commits template package by introducing support for parsing the Conventional Commits scopes into changelog sections, similarly to how they were previously organized. [Standard Version]: https://github.com/conventional-changelog/standard-version [Semantic Versioning]: https://semver.org Change-Id: I5bafa512daedc631baae951651c38c1c62046b0a Signed-off-by: Chris Kay <chris.kay@arm.com> 3 years ago			`}`