I forced pushed to my repo to get a rebase up there. The local repo is no longer around, and the remote repo is now being used. No commits have gone to the github repo since the force push. I’m running into odd errors with portions of code being reproduced twice and it happens in the massive build system too with that being very dificult to track down. Sadly, during the short window my system backup solution was down this happened.
I would like to revert the repo to the state the repo was in prior to the force push and rebase, as repairing the errors introduced is taking a long time. I can throw away the repo and patch, but just need my commits and would prefer to know that code at least works with the repo. Anyway to roll the repo back through other methods?
I think this is all from me using a rebase based merge strategy, while everyone else just follows the merge commit workflow, or the history of master is getting rewritten some how. If this a history rewritting issue how could I confirm that after the fact?