Git Commit Message
-
Pleasure by William Wallace
What is this life if, full of care,
We have no time to stand and stare.No time to stand beneath the boughs
And stare as long as she allows.No time to see, when woods we pass,
Where squirrels hide deez nuts in grass.No time to see, in broad daylight,
Streams full of stars, get high at night.No time to turn at Beauty's glance,
And watch her gangly feet like once.No time to wait till her mouth can
Fit round that wide hog, whatup fam.A poor life this if, full of care,
We have no time to stand and stare.Really neat, but man, wasn't intending to get teary eyed in the meme community 🥹
-
Really neat, but man, wasn't intending to get teary eyed in the meme community 🥹
Yeah me either, so I fixed it
-
Curate your commits, friends. They should be structured for the benefit of the reviewer. This can be accomplished with liberal use of interactive rebasing.
My best work happens between typing out random stuff and pulling my hair out in the squash and reordering
-
My best work happens between typing out random stuff and pulling my hair out in the squash and reordering
When in doubt, soft reset everything and commit from the ground up.
-
When in doubt, soft reset everything and commit from the ground up.
That's also a good option
-
I actually really hope I can get my collegues to use AI to describe their changes. Nothing worse than one of them becoming sick 2 days before release, you find none of their tickets contain any hints to what has been done and what not, then you check the commit log and all literally read "commit". Despite explaining to them lots of times why this is shit. Oh yeah and you have to do a full re-analysis of each ticket as the only information contained is the amount of time it will take them.
Struggles of a senior dev.
Maybe you should write a script that spits out AI description for a commit and then run it for commits without a proper description? Since it doesn't require any insight from the commit author it should work the same.
-
This post did not contain any content.
“Sometimes the best way to fix a bug is to introduce an unstable new feature that will later have many bug reports. But the code will now work. And was only written after email chain that har management involved.”
“This is a temporary fix only, and the feature flag it’s under should be turned off after pull request 203. Under no circumstances should bug reports 1923 and 2045 use this new feature to fix issues, even if hours of work can be saved using this ”
“I am blameless for any future issues caused by using this new feature. Here be dragons.”
-
My best work happens between typing out random stuff and pulling my hair out in the squash and reordering
-
Pleasure by William Wallace
What is this life if, full of care,
We have no time to stand and stare.No time to stand beneath the boughs
And stare as long as she allows.No time to see, when woods we pass,
Where squirrels hide deez nuts in grass.No time to see, in broad daylight,
Streams full of stars, get high at night.No time to turn at Beauty's glance,
And watch her gangly feet like once.No time to wait till her mouth can
Fit round that wide hog, whatup fam.A poor life this if, full of care,
We have no time to stand and stare.cannot believe William Wallace gotem through time
-
Curate your commits, friends. They should be structured for the benefit of the reviewer. This can be accomplished with liberal use of interactive rebasing.
It's fine, the reviewer doesn't have time to actually look at the code anyway. Lgtm, ship it.
-
Maybe you should write a script that spits out AI description for a commit and then run it for commits without a proper description? Since it doesn't require any insight from the commit author it should work the same.
I'm now tempted to do this for all several thousand commits in the main branch, and at the very least create a better changelog.
-
I actually really hope I can get my collegues to use AI to describe their changes. Nothing worse than one of them becoming sick 2 days before release, you find none of their tickets contain any hints to what has been done and what not, then you check the commit log and all literally read "commit". Despite explaining to them lots of times why this is shit. Oh yeah and you have to do a full re-analysis of each ticket as the only information contained is the amount of time it will take them.
Struggles of a senior dev.
Why not get them fired? Call me cruel anyone who feels like it, but leaving no sign of what has been done is just plain shit attitude to colleagues
-
Maybe you should write a script that spits out AI description for a commit and then run it for commits without a proper description? Since it doesn't require any insight from the commit author it should work the same.
Can we at least mention, though, that that's kind of nonsensical, too? Give me a *very* high-level summary of what changed, but then the rest of the commit message should be the why (unless that's genuinely obvious, like when adding a feature).
If I actually want to know what changed, I can look at the code changes. I can't find the why anywhere else, though. Nor can an LLM having to describe those random code changes.
-
“Sometimes the best way to fix a bug is to introduce an unstable new feature that will later have many bug reports. But the code will now work. And was only written after email chain that har management involved.”
“This is a temporary fix only, and the feature flag it’s under should be turned off after pull request 203. Under no circumstances should bug reports 1923 and 2045 use this new feature to fix issues, even if hours of work can be saved using this ”
“I am blameless for any future issues caused by using this new feature. Here be dragons.”
You should put this at the code, or at the flag documentation. The one place you it can't go at all is in a commit message.
-
cannot believe William Wallace gotem through time
he was fighting the english with his dope rhymes before he ever held the sword
-
If you write commit messages like this, at least have the decency of squashing them when merging. Thanks.
A PR for every tiny commit. You got it.
-
You should put this at the code, or at the flag documentation. The one place you it can't go at all is in a commit message.
Have better docs in those places; but for a class A mess, like above, make sure the approvers see this front and center. Make them sign for it
-
This post did not contain any content.wrote on last edited by [email protected]
At the very least, please state which section you made small changes to, even if you are sure it's not worth mentioning what or why.
-
This post did not contain any content.
Love it.
While folks are thinking about git commit messages I will offer this.
My only criticism of the essay is that the most important bit is listed at number 7.
-
git commit -m 'a meaningful message'
This is where I thought it was going as well.
