A team member keeps skipping the git hooks so he doesn’t have to fix the linting issues. What should I do?

1. Shit on him
2. Give him more work and less freedom
3. Steal his creds and inject more bugs into his code base
4. Revoke his access
5. Get him fired
6. Reject his PRs or mark them as "requires work"

Or just speak to him and understand why he does that

I wouldn't be surprised if IDE does that kind of service for him.
You should really ask what's happening, first of all.

Perhaps you can use a GitHub action to automatically run a code formatter which applies the suggestions from the linter on every commit? Then it doesn't matter if he has linting issues or not when he commits code.

ask him not to

@vintprox I’ll ask him. Before I rage on

Why is this in joke/meme?

@Root my mistake

Spoke with him, had a nice conversation. He said he will check.

You could also move the checks to the push hooks. It will also have the added benefit of allowing him to use git as a version manager in phases where the code is temporarily ugly. Otherwise he literally wouldn't be able to switch branches until he removes all trailing space.

@Lor-inc yeah. I don't get the notion of enforcing developer to install yet another linter on their machine, if the thing can be done once and for all in CI.
Having neat pipeline weights as gold. Luckily, existing services make it easy to start.

Could just code without linting like a badass fuckin server cowboy.

@vintprox Some ecosystems allow you to use project-specific tools without installing them globally.