828

submitted 1 day ago* (last edited 1 day ago) by Maven@lemmy.zip to c/programmer_humor@programming.dev

329 comments fedilink hide all child comments

Bonus

you are viewing a single comment's thread
view the rest of the comments

[-] subignition@fedia.io 5 points 21 hours ago

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 16 hours ago

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.