If it's a serious enough issue, GitHub staff can almost certainly still step in and manually restore all that stuff if needed.
And GitHub might have implemented something that let's them restore it after it wasn't possible before, as it's been 2 yrs since.
Lots of possibilities that might change the outcome if elastic is lucky
"In our case, however, they refuse to do that, citing undesirable side effects and the cost of resources. We even offered GitHub financial compensation for any resources required. But, sadly, they declined. They have other priorities than resurrecting the community of one of the oldest and most popular community projects on their platform."
Certainly possible they implemented a way to do this over the last 2 years.