This website works better with JavaScript.
Home
Explore
Help
Sign In
lukechilds
/
zap-desktop
mirror of
https://github.com/lukechilds/zap-desktop.git
Watch
1
Star
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.
1906
Commits
9
Branches
5
Tags
147 MiB
Branch:
master
gh-pages
l10n_master2
master
next
patch-1
renovate/babel-plugin-styled-components-1.x
renovate/lint-staged-8.x
renovate/prettier-1.x
renovate/react-icons-3.x
v0.1.0-beta
v0.1.1-beta
v0.2.0-beta
v0.2.1-beta
v0.2.2-beta
Branches
Tags
${ item.name }
Create tag
${ searchTerm }
Create branch
${ searchTerm }
from 'master'
${ noResults }
zap-desktop
/
.huskyrc
7 lines
108 B
Raw
Permalink
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": {
style(husky hooks): drop opt --in from husky hooks Make the linters run automatically for all users. This helps ensure that all contributions adhere to our practices.
7 years ago
"commit-msg": "commitlint --env HUSKY_GIT_PARAMS",
"pre-commit": "lint-staged"
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
}
}