-
Notifications
You must be signed in to change notification settings - Fork 29.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GIT_EDITOR set without asking and throwing error when I try amend a commit #150482
Comments
Also I see `git.useEditorAsCommitInput's default value is false and I don't have it set 🤷 |
Why do we need to explicitly set the git editor, isn't this something a user can configure in git settings to use VSCode as git editor? |
Related #150463 But I also agree that it looks strange to override expected config if git used in integrated terminal. |
FYI I think the fact it was on was a bug #150487, I don't have strong feelings about the setting itself. |
@bpasero, while users can indeed explicitly set their git editor to be VS Code, we are trying to make it easier for users to do so. The motivation/pattern here matches the one that drove the implementation of git askpass in VS Code. Happy to chat more if you want about this. |
Closing the issue as the |
Yeah understood, I came to the same conclusion about making it easier for users. |
|
@joyceerhl my issue is definitely fixed because the feature was reverted, not sure if it's getting added back this release with fixed setting @lszomoru? |
The feature will be added back for the next release, and the |
Normally I would use
git commit --amend
and fix the error in vim, from today I see this now:I see setting
$GIT_EDITOR
by default was intentional in #95266, I don't think we should do that; if a user is committing via the command line (not integrated git), you shouldn't touch the git commit editor unless opted into.The actual error here is because the path is wrong and is missing
gitEditor/
:Version: 1.68.0-insider (user setup)
Commit: 528ee1a
Date: 2022-05-26T05:16:43.433Z
Electron: 17.4.4
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.22000
The text was updated successfully, but these errors were encountered: