people who write one word commit messages

🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡

I have an alias for that

alias gc="git add . && git commit -m 'done' && git push"

I use it more than I care to mention

@kiki boooooooo

I mean its fine if you're the only dev (personal / small project)

but i'm in this big team and the guy commits with commit message the name of the branch itself? i mean what does that tell me? i know the branch name... cringe

@fullstackcircus you don't need to know. It won't matter in code review because you always examine the end result, and when it's lgtm and the pr is merged, it doesn't matter either — the thing works, that's all you have to know.

You wanna know something about the code? Read comments. You don't get it? Ask, then improve the comments with your newfound knowledge.

Oh, you don't write comments? That's a way bigger problem than commit messages.

by the way, self-documenting code is not an alternative to comments. It documents WHAT happens, but comments are there to explain WHY it happens. My code is always very terse, but I make up for it with extensive commenting.

You know you're doing it wrong when @Kiki and I agree on something.

Commits are pointless, rebase and merge, no commits 🤷‍♂️

Get good at PR's and Release notes, these matter more than a commit from 5 years ago.

Bro do we even need proper commit messages? Ask LLM to describe the git diff, LMAO

I know of a guy who wins this contest. He was developing a game engine for years and years, and he made nearly every single commit message just fucking 'ok'. Absolute madman!

git commit -m '👌'

@Liebranca he must have kept saying "ok" to himself

1. Enforce PR:s (no direct master commits)
2. Enforce all PR:s to be approved and squash-merged

Now you at least will not see any bullshit commits in master/main.

(Usually people will write a decent PR title even if their commit messages suck)

Splitting a unit of work up into a series of small but concise commits have been valuable for me.

I often need to cherry pick work between branches that’s corresponding to jira tickets a customer requested.

On my own & usually public projects, it’s often littered with “wip” that eventually leads to a commit message consisting of the feature name.

@asgs Well, that's deep...

Fucking clown world bruh