> I... usually just `git reset --hard` This is still risky if your ~/.git had uncommitted changes. I'll admit to being a little paranoid but I spent enough tim

> I... usually just `git reset --hard` This is still risky if your ~/.git had uncommitted changes. I'll admit to being a little paranoid but I spent enough time on the #git irc channel to learn that any advice that is potentially dangerous will _always_ be used in the dangerous fashion, often without knowledge of the risks. > although I think you meant GIT_WORK_TREE, not GIT_WORKDIR, right? Yeah, brain cramp on that one, sorry.