Hacker News Reader

Comment by jsnell | Hacker News Reader

And nobody on the team had a reasonably fresh checkout of the repo on their local machine?

To put it bluntly, this story does not sound credible. It's also one of the first things you say in the pitch, which taints everything you write later. I would suggest focusing on what you do well, not in making up stories about data loss with what you perceive as the competition.

(It's especially odd when Git isn't the obvious competition; Perforce is.)

View on HN

Swear to god, the story is true! We were able to restore most of the work because someone didn't pull the updates. (I should have added it in the story, didn't think it was important) But it was nerve wracking :')

But if someone DID pull the update, the old commits would have still been in their local repo and they could have run "git reflog" to retrieve them.

The person, who apparently googled some command sequence and happily entered them only to find out it overwrote the team's data, could just as easily have used those google skills to search for how to undo last git operation.

Obviously this person had all the privileges required to force push the previous commit in order to save the day. The old adage of never fact-checking a good story holds true however. Not sure it's a good selling point though, by nerd sniping everyone to explain in detail what the actual problem was no one will read to the end.

Reply on news.ycombinator.com