Hacker News new | ask | show | jobs
by nosefurhairdo 249 days ago
That's fine, but it shouldn't be enforced on all contributors. What matters is that failures don't get merged, not that they don't get committed.
1 comments

Yeah.

As long as "don't get merged" includes squashing so that whatever your (non)hooks didn't catch locally don't end up causing failures for rebases/merge conflict resolutions for others (assuming there are repo-level hooks people are expected to be using).