Comment

Comment by tjdetwiler

Githubs response:

Good news from GitHub: they have extracted the full list of SHA-1 before the forced push ! Many thanks to Nathan Witmer :-)

See below the full CSV with the SHA-1. He created as well a branch named 'recovery' that points to the candidate point for restoring the master branch.

Hope this will help to sort out the remaining repos.

Luca.

  > Hi Luca.
  >
  > Oh man, that sinking feeling!
  >
  > But, no worries: I've gone through each of the repos  listed above and done the following :
  >
  > * retrieved the SHA for the previous `master` before you force-pushed
  > * created a branch called `recovery` pointing to each former master
  >
  > In some cases, these are the same.
  >
  > I can go further and reset the master refs to their former shas if you'd like, or you can recover these yourself. To do so, in each repo:
  >
  > $ git fetch
  > $ git checkout master
  > $ git reset --hard origin/recovery
  > $ git push --force origin master
  >
  > I've attached a csv containing the shas (former master and forced master) for each branch, for your reference.
  >
  > Good luck!
  >
  > Nathan.
parent tjdetwiler 13 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton