You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lukewlms opened this issue
Feb 27, 2020
· 3 comments
· Fixed by #91732
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeeded
There appears to be a regression of this fix: #72573
VSCode Version: 1.42.1
OS Version: MacOS 10.14.6
Steps to Reproduce are identical to before:
Add VS Code as git commit editor (code --wait)
Perform a git commit
Edit the commit message in Code
Quickly close the commit message in Code, before autosave occurs
Result: git reports an empty commit message, even though Autosave is enabled in VS Code. This makes VS Code not very useful as a git commit message editor as I'm not certain it will actually save what I'm writing.
Does this issue occur when all extensions are disabled?: Yes
Thanks!
The text was updated successfully, but these errors were encountered:
As follows - 1 second with delay. Often I am pasting in a task identifier and immediately closing, which is very quick. (It seems the delay here should be irrelevant since I'm closing the file - autosave should always happen then, no?)
bpasero
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Feb 28, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugcandidateIssue identified as probable candidate for fixing in the next releaseverifiedVerification succeeded
There appears to be a regression of this fix: #72573
Steps to Reproduce are identical to before:
Result: git reports an empty commit message, even though Autosave is enabled in VS Code. This makes VS Code not very useful as a git commit message editor as I'm not certain it will actually save what I'm writing.
Does this issue occur when all extensions are disabled?: Yes
Thanks!
The text was updated successfully, but these errors were encountered: