Describe the Bug
In cursor editor, the following command in settings.json is ignored.
“git.enableSmartCommit”: false,
This results in cursor committing files that have not been staged, which is a serious problem leading to unreviewed code getting committed. Only staged code should be comitted. One more reason to consider switching back to vs code so we can follow approved workflow.
Steps to Reproduce
Have “git.enableSmartCommit”: false, in settings.json
In the Git tab, press Commit when there are no staged changes.
RESULT: Unstaged changes get committed.
Expected Behavior
If “git.enableSmartCommit”: false, in settings.json
Then unstaged changes should never get committed.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Additional Information
Using ubuntu in wsl under Windows 11.
“git.enableSmartCommit”: false, is present in user settings.json as shown by Cursor
If the commit button is pressed without staging changes, all changed files automtically stage and get committed. this does not happen in vs code, because it complies with user settings. This is dangerous because unstaged changes get comitted.
Does this stop you from using Cursor
No - Cursor works, but with this issue