reading through it, it sounds like they opened a project in VSCode, and it saw that there was a local git repo already initialized, with 3 months of changes uncommitted and not staged. So the options there are to stage the changes (git add) to be committed or discard the changes (git checkout -- .). I guess they chose the discard option thinking it was a notification and i guess the filename would be added to gitignore or something? Instead, it discarded the changes, and to the user, it looked like VSCode did rm -rf and not that this was the behavior of git. Since the changes were never committed, even git reflog can't save them.

[–] Mad_Punda@feddit.org 28 points 8 months ago (5 children)

From this issue: https://github.com/microsoft/vscode/issues/32459

It appears that the behavior actually included a git clean. Which is insane in my opinion. Not sure if they changed it since, but there’s definitely a dev defending it.

[–] Scoopta@programming.dev 2 points 8 months ago (1 children)

He said they're not going to change it, just make the dialog a lot more clear and add a second button to it that will only do a reset without the clean.

[–] BatmanAoD@programming.dev 6 points 8 months ago

The second button is actually a pretty major change!

load more comments (3 replies)