lukechilds
/
zap-desktop
mirror of https://github.com/lukechilds/zap-desktop.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1153 Commits
9 Branches
5 Tags
147 MiB
Tree: 297d93e80d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '297d93e80d'
${ noResults }
zap-desktop/.huskyrc

7 lines
163 B
Raw Normal View History

build(lint): lint/format in git pre-commit hook Currently we use eslint and prettier to lint and format code. However, running the linter is a manual step that is easy to forget. To improve this we run our lint scripts in a git pre-commit hook. This functionality is optional and can be enabled by adding a .opt-in file with a line `pre-commit`.
7 years ago
{
"hooks": {
build(lint): validate commit message format Automatically validate commit messages according to the Conventional Commit standard in a git commit-msg hook. This functionality is optional and can be enabled by adding a .opt-in file with a line `commit-msg`. See: - http://conventionalcommits.org/ - https://github.com/marionebl/commitlint
7 years ago
"commit-msg": "opt --in commit-msg --exec 'commitlint -E HUSKY_GIT_PARAMS'",
build(lint): lint/format in git pre-commit hook Currently we use eslint and prettier to lint and format code. However, running the linter is a manual step that is easy to forget. To improve this we run our lint scripts in a git pre-commit hook. This functionality is optional and can be enabled by adding a .opt-in file with a line `pre-commit`.
7 years ago
"pre-commit": "opt --in pre-commit --exec 'lint-staged'"
}
}