Pre commit hooks serve no other purpose than to be annoying.

Mmmm… false.

Sounds like you might be the reason that hook was set up.

Pre commit hooks are like doing validation in the frontend

@TheLastInteger it saves time since you get the warning before you try to push.

Last guy who I heard say this decided he didn't need to conform to the style guide because "his way" was better.

Yeah... It wasn't.

I love not being able to commit a because b has 'unused methods', I ONLY WANT TO COMMIT A FFS!

Time for double git mode lol

@ElectroArchiver then do not add b to the commit ;)

@ElectroArchiver Reminds me of my current employer’s doublethink:

“Use git to back up your work”
and
“Don’t commit broken code”

@Voxera I didn't select it to be commited . .

@Root 🤔

@ElectroArchiver Then its a badly created commit hook.

@Voxera Yes, and in my experience, many of them are.

@ElectroArchiver but that does mot mean that the idea of precomit hooks are but, just that most are bad at using them :)

And yes, that is a good reason to be weary of them and really think about what purpose you want them for.

They should be as a complement to push validation on the server and to avoid pushing something that will not be accepted anyways.

We have one that ensures that all commits start with what looks like a jira ticket id since all commits must be in reference to a jira.

It will not check if its a valid ticket, that is handled by the git server which will reject it if the jira does not exist, but it ensures that you did not forget to add it and that you formatted it in a way the server would understand at least, saving you time, especially if you where to push multiple commits, would be sad if the first was wrong :)

@Voxera Sure, though they should also work,..

some I have had the pleasure to use didn't work with GitHub Desktop for example,.. fun.

I agree. I wasn't there when they set it up, but no one uses them and they have some arbitrary and stupid rules like "no fullstop at the end of the sentence".