847

submitted 3 days ago* (last edited 3 days ago) by Maven@lemmy.zip to c/programmer_humor@programming.dev

259 comments fedilink hide all child comments

Bonus

you are viewing a single comment's thread
view the rest of the comments

[-] mox@lemmy.sdf.org 159 points 3 days ago* (last edited 3 days ago)

In case anyone else is wondering, or simply doesn't like reading screen shots of text, this is apparently a real report:

https://github.com/microsoft/vscode/issues/32405

[-] eating3645@lemmy.world 116 points 3 days ago

Steps to Reproduce:

1.Go near this fucking shit editor.

2.Commit the deadly sin of touching the source control options.

🤣

[-] jmcs@discuss.tchncs.de 88 points 3 days ago

Ignore the scary warning VS Code shows you when you press the button.

[-] SARGE@startrek.website 18 points 3 days ago

Having done exactly 0 research, I going to assume it's one of those "DO NOT PRESS OKAY UNLESS YOU ARE EXPERIENCED AND KNOW WHAT YOU ARE DOING" and someone went "pffft I know what I'm doing. click now what does this option do..."

[-] bamboo 28 points 3 days ago

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 29 points 3 days ago

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.

[-] MajorHavoc@programming.dev 12 points 2 days ago

It appears that the behavior actually included a git clean. Which is insane in my opinion.

Yeah. Building a convenient accessible context free way to run git clean...sure feels like the actions of someone who just wants to watch the world burn.

[-] bamboo 6 points 3 days ago

Yeah, it's unclear to me at the time if the dialogue box in the screenshot appeared when doing a select all operation, but it reads as though the OP dev didn't understand git, discarded their work, and got upset that it was an option.

Realistically if the dialogue box appeared, I'm not sure there would be anything else the IDE could do to prevent the dev from themselves. Perhaps reject operations affecting 5000 files? But then you'll just have someone with the same issue for 4000 files.

[-] Mad_Punda@feddit.org 13 points 3 days ago* (last edited 3 days ago)

The issue I linked has a very good analysis of the UX issues and several suggestions for fixing these. They went with a minor iteration on the original message box, which not only includes a clearer message and the number of files affected, but also defaults to not touching untracked files (while preserving the option to delete untracked files as before).

[-] Scoopta@programming.dev 2 points 3 days ago

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.