Git Commit Message
-
This post did not contain any content.
I once found a commit message in our commit history that just said, "i hate git..." bcz they hadn't changed anything, and I think it took a new line character and decided that they'd actually changed like 5 lines of code twhen they hadn't.
It was the funniest shit, someone who was a senior lead for like 9 years that had left, and 5 years later I find that...
-
I feel ya my home! This comment burns me with the feels of a thousand suns. I hate that it's related so much to this.
Totally agree with y'all.
I knew a guy who said that this was meaningless, because all the changes can be seen in the code. Like, are you really asking for a human diff!? 🤬
-
Totally agree with y'all.
I knew a guy who said that this was meaningless, because all the changes can be seen in the code. Like, are you really asking for a human diff!? 🤬
wrote on last edited by [email protected]The thing that really bugs me is that they will not learn, and that this is by design. They will never be expected to save a release. It always works like this: Someone calls in sick. I as senior dev am asked to help out. Often you hear "only the review process is open, all changes are done", sometimes even "there was a devdrop that was system tested". And so I agree, and let someone finish my tickets while I try to understand what they did. While doing so, I find something strange. I ask the system people about it (since SWD is sick). They shrug. I dig deeper. I find that my feeling was right, something is wrong. Explain in detail what I've found back to SYD: "Oh yeah we haven't tested this case. Good find!"
And then people wonder why I'm overworked.
-
Totally agree with y'all.
I knew a guy who said that this was meaningless, because all the changes can be seen in the code. Like, are you really asking for a human diff!? 🤬
Who needs a table of contents? Just read the book!
-
This post did not contain any content.
git commit -m "here is everything in this commit $(tar -czv . | base64)"
-
thank god now we've AI to do this
this is literally the only thing I think is acceptable for AI to do for developers.
nobody reads commit history anyway and they always go straight to blame to find out who to kick the fuck out of.
-
This post did not contain any content.
Curate your commits, friends. They should be structured for the benefit of the reviewer. This can be accomplished with liberal use of interactive rebasing.
-
This post did not contain any content.wrote on last edited by [email protected]
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. -
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
