Staging files popup after commit no longer stages files (= commit fails)

[prryplatypus]

Type: Bug

• Make a change to a file in a directory with Git setup
• Without staging it manually, write a commit message and press the commit button
• A popup will show up. Confirm that you'd like to stage all files.
• Observe how you get an error message and no changes get staged

VS Code version: Code - Insiders 1.92.0-insider (82104a3a6cf8713b81e5bbd97960dbf5c82a816a, 2024-07-05T00:00:00.000Z) OS version: Darwin arm64 23.5.0

System Info

|Item|Value| |---|---| |CPUs|Apple M3 Pro (12 x 2400)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|4, 3, 3| |Memory (System)|36.00GB (0.48GB free)| |Process Argv|--crash-reporter-id 427cb644-d627-42a0-aa3a-ac68ebc3e7d1| |Screen Reader|no| |VM|0%|

Extensions (22) - also tested with all extensions disabled and same result

Extension|Author (truncated)|Version ---|---|--- ruff|cha|2024.30.0 gitlens|eam|15.1.0 copilot|Git|1.211.0 copilot-chat|Git|0.17.0 discord-vscode|icr|5.8.0 debugpy|ms-|2024.7.11591012 python|ms-|2024.11.2024070501 vscode-pylance|ms-|2024.6.104 jupyter|ms-|2024.6.0 jupyter-keymap|ms-|1.1.2 remote-containers|ms-|0.377.0 remote-ssh|ms-|0.113.2024062515 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.88.2 remote-explorer|ms-|0.5.2024070409 material-icon-theme|PKi|5.4.2 run-on-save|puc|1.9.0 developer-theme-dark|Raj|5.0.0 svelte-vscode|sve|108.5.4 highlight-matching-tag|vin|0.11.0 intellicode-api-usage-examples|Vis|0.2.8 vscodeintellicode|Vis|1.3.1 (3 theme extensions excluded)

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256197 vsc_aa:30263845 vscod805:30301674 vsaa593cf:30376535 py29gd2263:31024238 c4g48928:30535728 962ge761:30841072 pythongtdpath:30726887 welcomedialogc:30812479 pythonnoceb:30776497 asynctok:30898717 dsvsc013:30777762 dsvsc014:30777825 dsvsc015:30821418 pythonregdiag2:30926734 pythonmypyd1:30859725 2e7ec940:31000449 pythontbext0:30879054 accentitlementst:30870582 dsvsc016:30879898 dsvsc017:30880771 dsvsc018:30880772 cppperfnew:30980852 pythonait:30973460 jchc7451:31067543 chatpanelt:31014475 g316j359:31013175 a69g1124:31018687 dvdeprecation:31040973 dwnewjupytercf:31046870 newcmakeconfigv2:31071590 nb_pri_only:31057983 nativerepl2:31071685 refactort:31084545 pythonrstrctxt:31089940 4930e709:31088354 ```

[prryplatypus]

Demo video

https://github.com/microsoft/vscode/assets/25409753/0c0c4142-2249-44b1-b6b0-ae6ef42f631c

[lszomoru]

Thank you very much for reporting this issue. Fix should be available in tomorrow's VS Code Insiders release.