I'd say it's "unfortunate" that getting myself into a confusing Git state was neither caused by having committed my changes accidentally, nor resolved by `git reset --hard`.
-
It's interesting, I was just contemplating exactly this! My confidence in my own ability to mentally track my Git state perfectly doesn't point at this being an explanation... but I know that VS Code is automatically doing some background updates to my Git repo...
By far the most likely explanation is still that I messed up somewhere. I'm much worse at Git than casual observers might guess, so I pin this on human error, but if it happens a few times, I'll start to think about alternative explanations.
-
-
But do you have the code you want even if git is in a mess? I’ve sometimes ended up there and copy it somewhere, hard reset and use diff to bring things back in.
-
I've been there many times before... But this particular code never reached Git, and then I did I `reset --hard` (because I was confused) and it got deleted. It took 20 irritating minutes to rewrite, anyway. I didn't need to redo the 40 minutes of thinking time, at least.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.