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.

[–] subignition@fedia.io 5 points 1 week 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 1 week 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 1 week 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.