Re:A set of best practices for JavaScript projects
by yes_or_gnome on Wednesday July 05, 2017 @12:10PM
(#14703614)
This is one reason why I find GitHub (especially, Enterprise) so frustrating. I want simple server-side githooks to verify that client-side hooks were used (or, at least a good forgery). I don't want to setup an additional CI environment just to run the most basic SED commands. Nor do I want to make my existing CI environment more complicated by merging disparate validations; unit test validation and commit validations.
Re:A set of best practices for JavaScript projects
by dav on Wednesday July 05, 2017 @09:14AM
(#14702112)
I built a simple system for some of our repos that fails the build if you don't have the shared team git hooks set up properly, and on failure directs the new engineers on how to fix the situation.
> A pre commit git hook gets triggered to run the linter[...]
Git hooks actually need to be set up to work, so this incurs overhead for onboarding.