It writes more informative commits than I could ever make so I’m just reading what it says and mostly copy/pasting completely most of the time, I write all of the changes I’ve made into an LLM with a large context window and it write a very detailed commit not just with a title but with bullet points describing each of the changes precisely
You realize you don’t need to list all your changes in the commit message, right? Anyone can blame or diff said changes.
The commit message is meant to be used for the high level stuff, the intent, representing / connecting progress towards a larger work item, and other important context from outside the codebase. Insert other reasons that aren’t saying literally what was changed if you feel I have missed something.
Also one should use their time better if they are spending so much time writing commit messages they feel the need to automate it. Commit messages are rarely read ever again (once merged, lets say), it is not okay to be spending a lot of time on them. That’s not an excuse to write bad commit messages, but you have to balance the time cost with expected utility.
And an addendum to the above. Describing what you did without reasoning, context, or other information that isnt captured within the changes itself makes your commit messages entirely useless. It makes IDE-inserted in-line blame information useless as well. Thus you are now wasting all the time you spend on commit messages, even if you spend less because it’s automated.
Yeah, good commit messages are about intent and context of a change - not what the change itself is. We can look at the diff for that. Just write a single line or two summarizing what the commit does, and everything else should be adding context on top that doesn’t directly exist in the codebase.
If a glorified autocomplete algorithm can write more informative and concise commit messages than you, the actual author behind the code, I think you need to sit down and think long and hard what that actually implies.
And what does it imply?
That an AI might be better at writing documentation than the average dev, who is largely inept at writing good documentation?
Understandably, as technical writing isn’t exactly a focus point or career growing thing for most devs. If it was, we would be writing much better code as well.
I’ve seen my peers work, they could use something like this. I’d welcome it.
And what does it imply?
it implies that the author of the code has no idea what they were doing.
I disagree. I am capable of writing a good commit message, I just don’t really want to. Depending on the change, formulating a concise text that includes all relevant information can be quite time consuming.
I can travel to Italy on foot. Will I do that? Of course not. What does it imply? That I’m incapable of moving my body? Of course not! It just means I’m too lazy to do it and that there are faster ways to get to the same goal.
Don’t ever call me a glorified autocomolete algorithm again
deleted by creator
If it’s faster to get an AI to write your commit messages than to write them yourself, your commit messages are too long. They should be one sentence.
And if one sentence isn’t enough, the commit has too many changes
Why don’t you know WHY you did something to the codebase that you now want to commit?
Relying on an LLM for that sounds like a crutch that you need to get rid of ASAP!
I’m really curious to see examples of commit messages.
And more details on how you achieved it, I’d like to give it a go myself, as some of my coworkers commit messages are less than stellar.
Does it write in the conventional commit formalism ?
deleted by creator
but it started splitting my commits in chunks
Wait, it can split commits ? I thought you “just” used a LLM to write the messages, but it can also act on the commits ?
How did you achieve this?
.
Im shocked at all the negativity, this seems like an obvious good usecase to me, and I’m someone who finds most AI predictive stuff useless.
I never take more than 3 sec on my commit messages, most of them are “fix bug”, “update lib”, “bump”. So it’s a pretty low bar for it to make better messages than mine.
Why don’t you spend time on commit messages though?
Okay, so to be honest, at first, I didn’t understand all the ❌negativity, but I shared this with a friend to get her take on the issue, and she 🕵️♀️clued me into the fact that webpack already does this with copilot and pull requests, and the results . . . speak for themselves.
Wow😅. I didn’t think it would be that bad. It seems that every example I find is just incorrect. I’ll look at the code. It will be a two line change, but the summary will be difficult to follow and often says things that are not part of the code changes. Then, there are also contradictions which make the pull requests harder to follow than if you just read the code with no other context. Darn it. I really thought this was a 🧊cool idea.
I’m definitely going to be sticking to writing my own commits as always.
so it reads proprietary code?
I don’t think that Lead and Projectmanager will love to hear that. At all.
y’all need to speak for your own companies. obviously some companies will not allow it, and I’d be personally skeptical of allowing it if I ran a company - but I also work at a place that effectively has given a quiet go-ahead to use it, with objectively talented engineers regularly making use of LLMs for boilerplate and other aspects of work.
obviously, there’s some calculus on when to use it, and you better damn inspect your outputs, but treating as a blanket rule that OP is a terrible employee at their company when you don’t know the company is rude as hell and uncalled for.
I think a lot of people in this thread are just upset/projecting because this is the first real hint that they’re not as much of a special-boy-programmer as they think. OP’s use case is fairly limited in scope, using the LLM for something it is actually pretty good for, and never implied he doesn’t check the output. They’ll never admit it, and will deflect, but they’re just worried.
