Git Commit Message
-
“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.
-
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.wrote on last edited by [email protected]Shakespeare may have coined a lot of English words, but only Wallace can claim deez nuts.
-
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.
And the blame has those commit messages. That is beside the fact that most authors may not even work there anymore
-
I keep putting that off, but maybe I should really dive into that.
Thanks for telling me about the TUI btw, I didn't know we had that too now! -
And the blame has those commit messages. That is beside the fact that most authors may not even work there anymore
I don't even waste my time anymore frankly. people just do a
git add .andgit commit -m "did some stuff".sorry, I've just worked with a lot of shitbag devs that honestly think of git as a flat filesystem that can't even properly branch or merge.
personally, I still put in clear commits and even do patch level adds. from what I have experienced though, using AI to generate those commit messages based on actual changes would be a godsend compared to the fuckery I've had to deal with.
-
“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.”
Nope. That's a temporary solution
. -
This post did not contain any content.
git commit -m "A spirit trapped within a tree, no mouth to scream or eyes to see. A cage of bark, a prison of wood. A thing of rage where nature stood."
-
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.
"Small changes to a few sections." There. Happy?
-
“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.”
“this is temporary test code that should be removed before delivery to the customer”
this is real
-
This post did not contain any content.
Always put a ticket number in the commit message. That can make it much easier later to find out what the context was for some weird solution.
-
git commit -m "A spirit trapped within a tree, no mouth to scream or eyes to see. A cage of bark, a prison of wood. A thing of rage where nature stood."
git commit -m "$(fortune | cowsay)" -
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.
wrote on last edited by [email protected]"Small changes to everything"
98 files changed, 7568 insertions(+), 1022 deletions(-) -
git commit -m "here is everything in this commit $(tar -czv . | base64)"
Go for broke
git commit -m "It works on my machine $(tar -ca . -C / | base64)" -
This post did not contain any content.wrote on last edited by [email protected]
For complex changes go with "self-explanatory" just to fuck with peoples' confidence
