the problem is that VS Code ran git clean if you clicked yes, which is completely idiotic behavior. No other git client, text editor, or IDE on the planet does that.

[–] ArbiterXero@lemmy.world 1 points 4 days ago (1 children)

Either way, waiting 3 months worth of work before a commit is the big mistake here.

[–] tyler@programming.dev 5 points 4 days ago (1 children)

I think they hadn't ever used git before, and according to at least one person in the linked issue, vs code might have auto initialized the git repository for the user.

[–] ArbiterXero@lemmy.world 2 points 4 days ago

In fairness, ALL git terms feel backwards at first.

[–] chunkystyles@sopuli.xyz 2 points 4 days ago (2 children)

Imperfect commits never existed when you squash.

[–] MajorHavoc@programming.dev 3 points 4 days ago

Interesting. I wouldn't know, because I code everything perfectly the first time.

Disclaimer: The above flagrant lie was brought to you by my also using rebase and squash to hide all of my mistakes.

[–] ArbiterXero@lemmy.world 3 points 4 days ago

Squash ftw. Simpler clearer history.