this post was submitted on 20 Nov 2024
876 points (97.6% liked)

Programmer Humor

19630 readers
964 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

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] subignition@fedia.io 5 points 2 days ago (1 children)

That's definitely fair, creating a repository in a non-empty directory could definitely suggest auto-committing the current state if it doesn't already. I don't use VSCode so I wouldn't know.

Although now that I think about it, that could have been the intention here but not automatic, if that's why 5k+ files were staged without the user explicitly staging them. Extra tragic if that's the case.

[–] T156@lemmy.world 1 points 2 days ago (1 children)

Although now that I think about it, that could have been the intention here but not automatic, if that's why 5k+ files were staged without the user explicitly staging them. Extra tragic if that's the case.

From the git discussions around the issue, it wasn't that the files were automatically staged, but that the "discard all changes" feature invoked a git clean, and also deleted untracked files.

Since OP's project wasn't tracked, it got detonated.

[–] WolfLink@sh.itjust.works 2 points 2 days ago

Since OP's project wasn't tracked, it got detonated.

This is the biggest part of the problem. Using git directly, it just ignores files that aren’t tracked.