Skip to content

Commit 0b9dcb4

Browse files
committed
Don't lint on git push
We run `npm run lint` every time we do a `git push`. This takes quite a long time, and the lint command has already been run when we created the commit in the first place. Could we instead skip this and rely on CI to tell us if we've failed to address a linting issue?
1 parent 66fd8ad commit 0b9dcb4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

extensions/ql-vscode/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1483,7 +1483,7 @@
14831483
"husky": {
14841484
"hooks": {
14851485
"pre-commit": "npm run format-staged",
1486-
"pre-push": "npm run lint && scripts/forbid-test-only"
1486+
"pre-push": "scripts/forbid-test-only"
14871487
}
14881488
},
14891489
"lint-staged": {

0 commit comments

Comments
 (0)