git horror
I nuked two unpushed commits and several uncommitted files by just pressing enter on the first result of `C-r res`.
Which wasn't to my surprise `make restart-db`, but `git reset --hard origin/staging`.
So, one panic attack later, i restored the commits via `git reflog`.
The uncommitted files could be recovered inside emacs via undo-tree-mode.
Thanks git and Emacs, for not making me write all this again.
#git #emacs #gitHorror
Which wasn't to my surprise `make restart-db`, but `git reset --hard origin/staging`.
So, one panic attack later, i restored the commits via `git reflog`.
The uncommitted files could be recovered inside emacs via undo-tree-mode.
Thanks git and Emacs, for not making me write all this again.
#git #emacs #gitHorror
git horror
The mistake actually happened in the terminal, by searching my command history and just pressing return on the first thing I suspected to be the thing I wanted to do.