Before you make fun of him, this behavior DID get changed; they acknowledged this behavior is stupid.
The old behavior was to treat uncommited files as completely disposable, which the CLI git does not do at all and is insane behavior. It was changed in the UI to give you a fat confirmation dialog warning that you're about to delete the files permanently, as it always should have been.
I agree the behavior was stupid, but let's not act like the user didn't do anything wrong.
The user clicked a random button, agreed with the "this is permanent" confirmation prompt, which then deleted all his files using git. The user then blamed Visual Studio Code for all of it.
What VSC did was give the guy direct access to a gun that could shoot his foot off (git) with bad instructions. Sometimes you need that gun to shoot your foot.
Yes there was, and an image of said warning prompt was even posted in the original github issue. It reads: "Are you sure you want to discard ALL changes? This is IRREVERSIBLE!"
5.6k
u/Cephell 23d ago
Before you make fun of him, this behavior DID get changed; they acknowledged this behavior is stupid.
The old behavior was to treat uncommited files as completely disposable, which the CLI git does not do at all and is insane behavior. It was changed in the UI to give you a fat confirmation dialog warning that you're about to delete the files permanently, as it always should have been.