Commit action first opens an editor on a non-existent file

[dc6c]

A recent VSCode update also updated edamagit to v0.6.64, and now commit first opens a blank editor on a non-existent file apparently named from a concatenation of path segments (e.g., if my workspace is D:\src\foo, then the file opened is named "srcfoo"). After I close the file, edamagit opens the familiar COMMIT_EDITMSG editor to enter my commit message.

I don't see anything odd in process.magit, just the "[0] git commit".

[bkaestner]

Can confirm, a downgrade to v0.6.62 removes the issue. This bug was introduced by 06eaf1d, as far as I can see. Given that the commit author was on Mac, this might be a Windows-specific issue.

VSCode version:

Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Datum: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
Betriebssystem: Windows_NT x64 10.0.19045

Affected edamagit version: v0.6.64.