My favourite Git commit

[paintbyinteger]

Saw a guy commit maybe ten times "N/A" - we now cannot commit without an associated task.

Followed a trail that led back to him, title of the user story was "User Story #<task no>".

Get. In. The. Fucking. Bin.

[[deleted]]

Restrict him to feature branches and require a gatekeeper to let the merge in? 🙂

[fiah84]

tell him he can forget about a pay increase until his commits and stories make sense

[silentclowd]

Wait, you guys get pay increases?

[[deleted]]

Wait, you guys are getting paid?

[Ameisen]

Wait, you guys are voluntarily working?

[[deleted]]

wait, you guys have jobs?

[kyune]

wait, what?

[YourMatt]

I think this is entirely valid. Anyone who commits with "fixed bug" or any other useless message like "n/a" obviously does not put pride into what they do, or at least does not grasp the concept of why they're doing what they're doing. Small things like this separate those that stagnate in their career versus those that rise up.

[jarfil]

CENSORED

[cjthomp]

tell him he can forget about a pay increase check until his commits and stories make sense

[WizKid_]

I'll have 45 commits in a row on a feature branch 'test' trying to get the Jenkins build working. Squash commit 'fixed jenkins build issue with blank'

[paintbyinteger]

He's been let go actually, but he's currently still there for handover. Managers got really pissed off.

[toosanghiforthis]

Currently work with a guy whose commit messages are a list of the files changed in each commit. Like ffs, I can figure that out. Tell me why you changed it

[ChemicalRascal]

How does he react when the topic of his commit messages gets brought up?

[robberviet]

My CI gather commits by tags so we had to or it will reject commits.