Comments by "" (@d3stinYwOw) on "The dangers of precommit hooks" video.

  1.  @manoellopes211  Probably you didn't worked in a place where you needed to have at least task ID as part of commit msg ;)
    3
  2. Then set it properly and publish the config for it, to be sure that everybody have same pre-commit/pre-push setup.
    1
  3. As well as making it just a nick harder to commit without passing linter and formatting check, because, as good as editors are, people forget to format according to accepted way in repo. I can see it at work sometimes, where CI picked up that formatting was off, or lint, and next few commits were made just to fix those, already in PR.
    1
  4. Just don't use crappy pre-commit engines like husky. use pre-commit, and have in CI just check as well. It's easy to have proper, repeatable environment, but you can't use JS :)
    1
  5.  @merionis  to have something that flies for example.
    1
  6.  @emeraldbonsai  CI messing with code? Hell nah.
    1
  7. auto import is the devil.
    1