Closed janpanschab closed 8 years ago
I find this quite disturbing. Especially during gulp-stack development. What about having it as a pre-push hook/script?
Rationale:
build
on every commit is pretty time consumingThe push hook would still catch any errors before pushing them to the repo without sacrificing the productivity.
build
on every commit is pretty time consuming
I like it as pre-commit hook, because it prevent broken commits.
I often edit stuff which doesn’t deal with build related files
If you are sure you doesn’t deal with build related files you can force a commit with --no-verify
I can see your point. Still I’d like to discuss it on the next 1:1 meeting. Closing the issue :)
How about running only linting tasks on this hook?
Change to pre-push hook.
Add build task to pre-commit hook. http://elijahmanor.com/npm-precommit-scripts/