866

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

336 comments fedilink hide all child comments

Bonus

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

[-] conciselyverbose@sh.itjust.works 19 points 3 days ago

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.

[-] subignition@fedia.io 5 points 2 days 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 2 days 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.