Option to Require Explicit Staging Before Commit (Disable Auto-Stage on Commit)

[tiago-vincit]

Currently, when committing in Zed, if no changes are staged, all changes are automatically staged and committed. This is similar to git commit -a. However, many users (especially those coming from editors like VS Code or JetBrains IDEs) prefer a workflow where only explicitly staged changes are committed, and nothing is auto-staged by default.

Please add an option in Zed’s settings to require explicit staging before committing. With this option enabled:

• If nothing is staged, attempting to commit should either do nothing or prompt the user to stage changes, but should not auto-stage all changes.
• Only staged changes should ever be committed.

Alternatively, add a confirmation dialog to make sure the user wants to commit all changes when none are selected.

Benefits:

• Prevents accidental commits of unrelated changes.
• Aligns with workflows in other editors and with standard git CLI behavior (when not using -a).
• Gives users more control and confidence over their commits.

[agladfield]

+1 There have been several times where I feel like I'm commit just a changed file, and because I work in a large monorepo and there is yet to be a git file filter implementation, I end up committing swaths of stuff in disparate folders that I don't want to commit. It's a serious headache and slows me down when the point of Zed is to enable me to work faster.