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`.
Not this time, sadly. The mistake was that I was convinced I'd made Git aware of my changes... and I hadn't.
-
-
This Tweet is unavailable.
-
That would be useful.
End of 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.