I'm usually the "git guy" so having something like this to refer to when people ask me about such things will be really useful. Thanks! One of the problems I h

I'm usually the "git guy" so having something like this to refer to when people ask me about such things will be really useful. Thanks! One of the problems I have is figuring out how people get themselves into such situations. Like if someone submits a merge request and their branch looks like it's been merged into itself with one side rebased or something. When I ask them what they did they have invariably forgotten. If someone cooked a dish that was too salty I'd be able to tell them "try putting less salt in less time". I wish I could do the same with git. Although upon typing this I'm thinking perhaps I could figure it out by looking at their reflog? But that involves accessing their computer or walking them through it which would probably confuse them even more.