Hey, we’ve changed it as most users preferred more concise messages compared to the old ones, but we are hoping to add more control over this in an upcoming hotfix soon!
I’ve been really enjoying using Cursor so far, but I have to ask: who decided it was a good idea to make commit messages less detailed? It’s hard to imagine users actually requesting less detail in their commit messages while commit messages are all about giving as much detail as possible about the changes. Cursor’s commit messages were a huge improvement over Copilot’s, and I really hope the detailed versions make a comeback soon.
Also, I’ve noticed that commit messages are now extremely slow—sometimes taking up to 30 seconds for a small file, whereas before it only took 2–3 seconds. Any idea what’s causing this issue? Thanks!
I prefer short commit message - a title of the commit. What the point to write super detailed commit title? Who will read all that commit stories? And the example more looks like PR than a commit.
Maybe in my practice commits are smaller and has short titles just in super-rare case where somebody needs to find something in the history.
Same. I disagree a commit message is about giving as much detail as possible. If it were as much detail as possible you’d put every line of code in it. It’s about giving a useful summary of the changes.
Alright, fair enough. It seems like we really need a feature so anyone can customize the detail level of commits. I love detailed commits so I can search for a change. I think it also depends on how often you commit. If you commit literally every change you make right away, smaller commit messages might be better but as someone who implements a feature across files, a detailed commit message on what changed where and why is great. Because sometimes I tend to change code when I cange my mind about an implementation and having that change already commited is unnecessary. Also bundling commits that reach across files makes sense so again, it’s nice to have a good summary. But I get why some people would like to have shorter commit messages. I only really commit when I’m taking a break because committing for me is a chore that’s not contributing any kind of value other than having your code safe and I don’t want to lose focus while coding. Hope we get control of the detail depth soon.
Copilot have copilot-commit-message-instructions.md which get applied just for commit message generation. It allow all the customization that you want/need. I think that would be the best approach. (or a field in the settings). But personally I always prefer file over settings as you can commit them with your project and they can be unique for each of them.
Also Copilot to generate commit message is much better. It’s always complete and short. Cursor I make 2 changes, it will only create a commit that talk about one of the 2 changes.
So usually I have both VS Code and Cursor open, I will use VS Code to generate the commit and push it.
