Change Details

**Motivation** Utilize eslint/stylelint/etc on pre-push git hook so that I, as a developer, get all linting errors (possibly most or some of them fixed automatically) before I submit my changes to gerrit just to learn after 20 minutes (average time for our build) to learn about a missing space. **Suggested solution** Once {T224398} is done. We can think of hooking eslint fix into pre-push hook.

**Motivation** Utilize eslint/stylelint/etc on pre-commit git hook so that I, as a developer, get all linting errors (possibly most or some of them fixed automatically) before I submit my changes to gerrit just to learn after 20 minutes (average time for our build) to learn about a missing space. **Suggested solution** Once {T224398} is done, we can think of hooking one of the following combinations: 1) have npm fix run alone as a pre-commit hook 2) have npm test + fix run automatically 3) only run npm test as part of the hook, developer runs grunt fix when needed (Feedback is to be collected from other wikidata developers as to which is the best option)

**Motivation** Utilize eslint/stylelint/etc on pre-pushcommit git hook so that I, as a developer, get all linting errors (possibly most or some of them fixed automatically) before I submit my changes to gerrit just to learn after 20 minutes (average time for our build) to learn about a missing space. **Suggested solution** Once {T224398} is done., we can think of hooking one of the following combinations: 1) have npm fix run alone as a pre-commit hook 2) have npm test + fix run automatically 3) only run npm test as part of the hook, We can think of hooking eslint fix into pre-push hook.developer runs grunt fix when needed (Feedback is to be collected from other wikidata developers as to which is the best option)