Looks like they weren’t staged. He clicked on the staging option, it showed it would stage thousands of files, he said “hey I should fix my .gitignore” and clicked on what looked like either a “don’t stage” or a “forget” button, and it was a “checkout --force” button.
The most impressive thing is all the people doubling down on the idea that a “checkout --force” button in a main interaction screen is a great idea, there’s nothing wrong with the software, and the user is a moron.
Even back in my super noob days, I’d keep known good working versions of the files in separate folders. I basically invented my own terrible source control system before I knew anything about svn or git.
If the files were already staged then git should have blobs in the git folder, so they should be recoverable.
Looks like they weren’t staged. He clicked on the staging option, it showed it would stage thousands of files, he said “hey I should fix my .gitignore” and clicked on what looked like either a “don’t stage” or a “forget” button, and it was a “checkout --force” button.
The most impressive thing is all the people doubling down on the idea that a “checkout --force” button in a main interaction screen is a great idea, there’s nothing wrong with the software, and the user is a moron.
“discard changes” button - the 5000 “new file created” changes, specifically.
Did you read the thread? There was a bug that deleted all files even ones unassociated with git.
Sounds like they weren’t even using version control, and had no business anywhere near a project that size.
Lol. That’s a really good point, actually.
I add version control around file number 3200…
(I’m kidding. Writing even a couple lines without version control makes my eye twitch.)
Even back in my super noob days, I’d keep known good working versions of the files in separate folders. I basically invented my own terrible source control system before I knew anything about svn or git.
Yeah. Same here. We learned to mistrust computers very early.