Not on this occasion... but I hadn't checked until you suggested it!
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`.
-
-
This Tweet is unavailable.
-
- Show replies
-
-
-
Just throw away your laptop and buy a new one.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
rm -rf .git && git init && git add . && git commit -am “Initial commit”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
Not this time, sadly. The mistake was that I was convinced I'd made Git aware of my changes... and I hadn't.
- Show replies
-
-
-
I've seen race conditions caused by multiple git-aware tools pointing at the same repo simultaneously, usually while I rebase or do other weird things. When that has happened to me, the only solution has been manually fiddling with the git filesystem representation.
-
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...
- Show replies
New conversation -
-
-
I have this: "git config --global alias.reset-hard '!git tag -f RESET_HARD_STASH $(git stash create); git reset --hard'" Now git reset-hard is a safe alias of git reset --hard. If I screw up I can always do 'git stash apply RESET_HARD_STASH' to recover the wiped out changes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.