this post was submitted on 20 Nov 2024
694 points (97.4% liked)
Programmer Humor
19623 readers
2164 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You shouldn't be taking ownership of files and then deleting them without communication a hell of a lot better than that.
I understand what happened. I'm saying that if you're going to delete stuff that was there before the software was, your flow to adding a project should include suggesting a base level commit of everything that's there already.
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.
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.
This is the biggest part of the problem. Using git directly, it just ignores files that aren’t tracked.