Hacker News new | past | comments | ask | show | jobs | submit login

Possible solution: mandatory pre-commit or pre-push hook that lints the code.



We have this, but have a handful of devs who can't be bothered to install the hooks locally so deal with their PRs by fixing one linter error at a time and pushing a new commit to see what fails in the CI.


I’m glad I’m not the only one who has to put up with fools like this. Not only the insane git log, but the compute for those actions isn’t free either. Just run the damn precommit hooks, it literally fixes the issues for you!


you do squash though, right? ...right?


Their fault then. It's their time afterall.

It cannot be much easier than to install pre-commit hooks.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: