3 ms·
Because commits should be small and fast, and always work, like a save. If you’re running a multi second process during commit it’s going to get ripped out.
by wiredfool 2y ago
Because commits should be small and fast, and always work, like a save. If you’re running a multi second process during commit it’s going to get ripped out.
- zahlman 2y agoMy thinking is that the linter only has to operate on the code that was actually checked in. And just how many things are you checking about it, anyway?
- orra 2y agoAhah! I worked on a project which used dotnet format in a commit hook. That was a frustrating experience, trying to rebase code. (Unlike most formatters which are instant, dotnet format takes at least half a minute, because it performs a build just to format your code.)