I'm not sure about this at all. Most checks should be in the CI but git hooks allow a team to add rules without affecting all teams at once. When rules turn ou

I'm not sure about this at all. Most checks should be in the CI but git hooks allow a team to add rules without affecting all teams at once. When rules turn out good they can be enforced on everybody via CI. Even a single team might have dozens of machines, so they don't want to roll out git hooks manually. This is the niche use case I can think of. Still, it exploits git to do things it is not made for. This is asking for trouble elsewhere.