S
Shrek Tan
The auto-commit message feature has two main issues:
Ignores Staged Files: It creates commit messages based on all modified files, not just the ones I've staged. This makes the messages inaccurate when I'm making multiple, smaller commits.
Lacks Detail: The messages are always very short and don't explain the changes well, even for complex commits.
Suggestions:
Please make the auto-commit messages respect the staged files.
Consider making the messages more descriptive, especially for larger changes.
E
Emre Karanfil
While preparing a commit through the Windsurf interface, an automatic commit message is expected to be generated. However, a static message saying “Please provide the code changes you'd like me to summarize in a commit message.” is always displayed, and no summary is generated based on the actual changes.
Additionally, every time I interact with the buttons, I receive the following warnings:
I cannot generate a commit message without seeing the code changes. Please provide the file diffs or changes you want me to summarize.
Please share the code changes you'd like me to summarize in a commit message.
Is there something I’m missing, or is this a bug? How can I resolve this?
Windsurf Version: 1.7.2
Windsurf Extension Version: 1.46.0
Windsurf Commit: 619323b3cdd4a88a75f3b5fa39dba02c3b9e14a9
VSCode OSS Version: 1.98.0
Commit: 619323b3cdd4a88a75f3b5fa39dba02c3b9e14a9
Date: 2025-04-27T04:29:22.564Z
Electron: 34.2.0
ElectronBuildId: undefined
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Darwin arm64 24.4.0
J
John Galt
Add the following to your general or local Windsurf rules to have a detailed git commit message created automatically at the end of every prompt.
================
git commit message suggestion rule:
After completion of a prompt that required the change of one or more files, generate an appropriate git commit message for the recent prompt changes using git best practices but do not include any file paths or line references. Each item in the commit body text should be prepended with "- ". Also include the unformated recent user prompt at the bottom of the commit message body without attempting to add a timestamp while prepending it with "Received prompt: ". Don't include actual git commands in the message. The message should be formatted in such a way that it can be easily copied and then pasted into editors' built-in Git Commit GUI.
Y
Yona
In Windows, clicking the button does not generate any message
K
Kai
Thank you so much. Really appreciate it. Keep up the good work guys 👍🏻👍🏻
John
100 Years Later
o
ooooooooo
In Cursor and Copilot this feature is free. So weird to see that it's paywalled in Windsurf.
lin mo
could you add a prefix of each commit log? such as: feat:, fix:, chore:,
Rohan Phadte
complete
This is now available in Windsurf Wave 6!
M
Marlen Brunner
Rohan Phadte Is that going to be available via the command menu as well?
Windsurf Version: 1.6.2
Codeium Version: 1.42.4
Codeium Commit: 1eabbe10abd0f4843e53460086ba8422a1aebe02
VSCode OSS Version: 1.97.0
Commit: 1eabbe10abd0f4843e53460086ba8422a1aebe02
Date: 2025-04-04T02:02:16.017Z
Electron: 32.2.7
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.11.0-21-generic
Rohan Phadte
Marlen Brunner This is a fix that will be in a release very soon (~Monday/Tuesday).
R
Ryan zayne
Rohan Phadte sadly clicking it doesn't do anything
o
ooooooooo
Rohan Phadte In Cursor and Copilot this feature is free. So weird to see that it's paywalled in Windsurf.
Hannes Burrichter
Rohan Phadte
Thank you for your work but this feature does not work very well for us.
Windsurf creates a commit message for all changes, not just for the staged changes. So precisely commiting a few changes is not possible with this feature at the moment.
Also windsurf does not follow the conventional commit standard. The messages are not very useful, compared to Cursor.
Hai Nguyen
Rohan Phadte
TLDR: I still have to commit using Cascade after this feature is released.
As I have already suggested, I have to tell Cascade again and again to read the previous commits (
git log --oneline -5
) to give it the context for a proper message following the convention. The Git commit message generation feature should include customizable prompts, similar to the global rule feature, to enhance its flexibility and user control. I agree with Hannes Burrichter. I always need the commit message for the staged file, which is quite straightforward. Why do I need commit messages for all the working files? By the way, it's a pretty simple function and shouldn't incur extra charges.
t
trynewaithings
Rohan Phadte how could I make it generate commit message for added files only (not all changed files, which is what it currently takes into the generating the commit message as far as I noticed)
E
Esteban
+1, the newly added Generate commit should only take staged changes imo. I don't see it being very useful if it tries to make sense of all unstaged files.
Load More
→