870

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

339 comments fedilink hide all child comments

Bonus

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

[-] Pyro@programming.dev 10 points 1 month ago* (last edited 1 month ago)

~~He wouldn't have seen the "Discard Changes" button at all if source control wasn't already setup (and detected by VSCode).~~

~~No sane program will delete files when you initialize source control either.~~

As I found later, VSCode did have weird behaviors with source control back then. My experience is more with the latest versions.

[-] LordPassionFruit@lemm.ee 12 points 1 month ago

My sibling ran into this issue once. I'm not sure if it's a setting or a default, but vscode would assume they were working in a blank repo until they made a commit.

Sounds like this person had the project (without source control) in another IDE, tried out VSCode, and it assumed that it was all 'changes'. I don't use VSCode, do I can't say for certain, but I know my sibling lost ~4 hours of project set up for the same reason (though they immediately realized it was their fault).