866
Microsoft Please Fix
(lemmy.zip)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Nov 2024
866 points (97.5% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
🤣
I dunno, “discard changes” is usually not the same as “delete all files”
What exactly do you think discard means?
“Changes” are not the same thing as “files”.
I’d expect that files that are not in version control would not be touched.
Yeah. That's discussed in more detail in the code change that resulted from the issue report.
It's a ballsy move by the VSCode team to not only include
git cleanbut to keep it after numerous issue reports.As others discussed in that thread,
git cleanhas no business being offered in a graphical menu where a git novice may find it.That said, I do think the expanded warning mesage they added addresses the issue by calling out that whatever
gitmay think, the user is about to lose some files.Apparently, it means changes to the directory structure and what files are in them, not changes within the files themselves. It really ought to be more clear about this.
Yeah. They did substantially modify the message to make it much clearer, thankfully.
It means both.
"Changes" encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.
It can also be all of them at the same time, which is why VSCode uses "Changes" instead of "Files".
And the terminology is misleading, resulting in problems. shrug.
I find it difficult to lay the blame with VSCode when the terminology belongs to git, which (even 7 years ago) was an industry standard technology.
People using tools they don't understand and plowing ahead through scary warnings will always encounter problems.
Wasn't the issue that it deleted a bunch of preexisting untracked files? So old untracked files.