[debaserab2]

> I used to work at a company where someone (we never figured out who)

Wouldn't this be trivially solvable by git bisecting your deploy branch?

[btilly]

No, because git bisect operates off of the information in the history. And thanks to the bad rebase, the history no longer existed in the branch.

[lifeisstillgood]

Just clarifying ... they took a version of master from say a month ago, did their work on it, then, they force pushed their work out, wiping everyone else's work that was added to master since one month ago?

I mean that's the equivalent of reversing your JCB through a house on a building site because "the house was not there a week ago when I last moved the JCB".

or am I missing something?

[yxhuvud]

But that make no sense, as the second someone pulls from that branch it would be noticed.

[latexr]

Wasn’t `git reflog` viable?