git commit -m "minor fixes" +26858 -69429
git commit -m "minor fixes" +26858 -69429
69Meanwhile I'm like
10
I've seen a changelog that said "Introduced some bugs, so we can fix them later".
It was a joke, but true nonetheless.
56It was a joke
Narrator: Of course, it wasn't.
7
Good opportunity to say how annoying are update notes like “We are continuing to improve our application. We fixed a couple more issues to make it more stable”. Corporate style, uselessness and the fact that this update can contain some stupid redesign is disgusting.
49"We are constantly improving our application. Please keep updates turned on."
11I've reached a point where I avoid these types of updates. An update post like that either means nothing important changed or they're up to something.
A while ago I saw that style of patch notes, updated an app, and suddenly I can't use it anymore because it got limited to a maximum of 2 devices. Another time I updated an app putting a harmless "we improved the user experience" message, they put dark mode behind a paywall. This isn't counting the number of times an app got redesigned to make the user experience worse for no reason. Maybe they wanted to justify hiring 5 UI/UX interns in that quarter or something.
The patch notes look harmless, but my god, they are usually up to something.
6Yeah. I do the same. That "we are making improvements" text is corporate for "we don't have anything remotely close to change management or quality assurance".
2
My lawyer friend assures me that if a company does that and their updates break my workflow, I'm legally entitled to throw one brick though one of their office windows, as long as it is during strandard working hours and into an unoccupied office. (I'm joking, obviously. But we could maybe work on passing such a law...)
2I'm done with programs that need meaningless updates like this every day. All my patience for that was used up with flash and java.
1
Yep, we also got one of these:
and pretty sure the "y" was typo.
46Straight to jail
31We have the best commit log in the world, because of jail.
7Could be worse. I've got a repo where 30 commits after eachother are just ".". Nothing else.
6More than anybody I'd like seeing justice be done.
Be we need him, he fixes our javascript ...
1
I was hoping one would be nae nae
1
The people that do this are either inept or experts, no inbetween
31just a hobbyist here, but wouldn't this actually be a good use for AI? Just copy the code and "provide a git committ title for this code"?
2AI might be able to write what you did but not why you did it
7Yep this is already a thing built into code editors like webstorm :)
1
My personal favorite used to be "Long time no commit"
31I call that a checkpoint when I do it. But I do that on my branch that will eventually be squash merged.
9I like to go for dark jam poetry, in those commits.
'why is anything? can it be? desolation - oh wait, that variable is mistyped!'
6
Every one is using AI to make funny pictures. This is what they should be using it for. Look at my diff, generate a commit message.
29If you don't know what you've done within a commit, it probably shouldn't be a single commit, with or without AI Although if you're talking about using AI to make funny commit-messages...
13Ok Eugene, we get it.
1Doesn't mean you can't use text inference to make your messages better
1
Funny enough, that's a feature of GitHub copilot: https://code.visualstudio.com/docs/editor/github-copilot#_generate-git-commit-messages
https://devblogs.microsoft.com/visualstudio/write-your-git-commits-with-github-copilot/
3We're doing that too :)
1
My commits when merged into main generally read like
[Ticket-123] Summary of what was done. Eg: Return user foo property in bar endpoint
- update bar view to return new foo key
- update foobrinator to determine foo property
- update tests
It takes an extra minute or two but it's more informative for the team / future me.
25Mine look similar except the body is mostly "the X was doing Y, but it should've been doing Z" or "the docs say bla, $link". I try to separate the individual "update A to do B" in separate commits, but sometimes it just isn't possible.
3
git commit -m 'initial commit' git commit --amend git commit --amend git commit --amend git commit --amend .... git commit --amend
23Could be worse:
git commit --allow-empty-message -m ""22kinda like on google play how it says "what's new: no information from the developer" or "what's new: we regularly update our app to fix bugs, improve performance and add new features".
22All praise our lord and saviour
git rebase -i!21amen!
2--amend
3
I fckd up a
git rebase -itoday withgit commit -a --amend...Thankfully
git reflogallowed me to assemble the branch again ... from pieces.1
do_the_thing() { git commit -am "$(date)" git push }9And I'd bet stuff is still broken!
9Yeah. Definitely. If it was fixed there would be a commit with log 'works now. WTF?!'
7
Maybe they tastefully squash merge when they pr/merge into main.
7The don't... 😭
2
At least none of it is WIP...
7Meh. At least you know "WIP" means you shouldn't expect that particular commit to work.
6It just has to work enough.
3
There are some, but not in the picture 🙃
3Perhaps, but there will a bunch of TODO comments so pick your poison
2
I remember making a bunch of fixes and calling them after Star Wars movies with the thing I'm fixing or what was broken as the noun.
3So you were part of the git clone wars?
2Ah the historian.
1
Could you give an example? "Star Wars: The Bug Fix"?
-2
Why user standard version and conventional commits in the first place? When this is only a fraction of purposeful commit messages
3Because if you are creating a changelog automatically based on the commit messages it will be very public and that user will look bad.
https://www.conventionalcommits.org/en/about/#tooling-for-conventional-commits
2
Commit messages of my personal projects are filled with just "fix". Life is too short to write a proper commit message
2About what my coworkers do but even worse with stuff like "save" and "fix"
1What The Commit provides a list of all-purpose messages to randomly select between. Would these be better?
1🫣 $(rm -rvf .)
1
When there's a limit to the size of a commit message it does make it difficult to actually list all the changes, so sometimes this is all you can write.
I know in theory you're meant to commit little and often, but in practice it doesn't always work out that way.
-3Even if you have a big commit, you can always write something more descriptive than this. And commit messages can be huge, so the limit shouldn't be an excuse to write a useless message.
10For those wondering how to exceed the 70 (80) recommended character limit and still follow best practices:
- Write the title on the first line, keep below 70 characters.
- Make two (2) newlines
- Write one or more descriptive paragraphs.
The first line will be shown as commit message, and the full text can usually be viewed by checking out the commit. Sentences can span multiple lines, but try to keep the line length below 70 characters for best readability.
This off the top of my head, so feel free to correct me if I've misremembered the best practices.
9