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).
That’s basically how I did it.
To properly learn it using this method, create a directory that contains only text files and sub directories and treat it like a real project. Add files, delete them, play around with updating the repository. Try and go back a few updates and see how the things react. Since it’s not a real project there’s no risk of loss, but you’ll still get to see the effects of what you do.
I work with Java. And I’m definitely ‘rose tinted glasses’ because I also learned to code in Java. But I’m the opposite.
Do you use Java at home?
Fuck no, I want to stay sane.
My dad tells stories of snowstorms back in the 70s & 80s where they would leave their truck at the end of the driveway with the keys in it and unlocked.
We live very rural (my grandparents were my neighbours growing up), and snowstorms could get bad. So everyone left their vehicles out with the keys in case someone broke down on the side of the road so that they could hop in the truck and turn it on to stay warm. Never had a vehicle so much as damaged, much less stolen.