Council— In preparing for tomorrow morning’s Stylesheets meeting, I was preparing to commit some changes to odd2odds.xsl on my fork. I noticed my fork had some old commits on it that I didn’t want to send with a pull request (old practice code I wrote, not useful to us), so I decided to destroy my fork and create a new one. The problem was—I went online to do it, thought I was accessing my forked origin to delete—I was on the wrong page. Evidently I deleted the remote origin repo because I can’t access it any more (and presumably no one can). I immediately wrote for help to GitHub support to try to restore our Stylesheets repo as it was at 11:30pm EST on November 1. I’m waiting to hear from them, but in the meantime, I wonder if we have a full copy of the repo with the issues. I am hoping that this is known territory to someone among us, that the good people at GitHub can help, that I haven’t destroyed everything! I am reasonably confident we can put the files back as they were tonight—I have them pulled in locally anyway. I am anxious about the tickets, and extremely upset. Anyway, you all need to know what just happened, and I hope we can repair it. It hardly bears mentioning that I think I have a fix for the issue we’re to discuss tomorrow. We need the Stylesheets repo! Elisa, worried sick and anxiously awaiting word from GitHub. -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/
Apparently this is known territory to GitHub—and I’m following the advice here: https://stackoverflow.com/questions/9247961/recover-a-deleted-repository-git... https://stackoverflow.com/questions/9247961/recover-a-deleted-repository-git... I’m writing to support@github.com and hoping someone will respond there as quickly as the people here indicate. Elisa
On Nov 1, 2017, at 11:57 PM, Elisa Beshero-Bondar
wrote: Council— In preparing for tomorrow morning’s Stylesheets meeting, I was preparing to commit some changes to odd2odds.xsl on my fork. I noticed my fork had some old commits on it that I didn’t want to send with a pull request (old practice code I wrote, not useful to us), so I decided to destroy my fork and create a new one. The problem was—I went online to do it, thought I was accessing my forked origin to delete—I was on the wrong page. Evidently I deleted the remote origin repo because I can’t access it any more (and presumably no one can). I immediately wrote for help to GitHub support to try to restore our Stylesheets repo as it was at 11:30pm EST on November 1. I’m waiting to hear from them, but in the meantime, I wonder if we have a full copy of the repo with the issues. I am hoping that this is known territory to someone among us, that the good people at GitHub can help, that I haven’t destroyed everything!
I am reasonably confident we can put the files back as they were tonight—I have them pulled in locally anyway. I am anxious about the tickets, and extremely upset. Anyway, you all need to know what just happened, and I hope we can repair it.
It hardly bears mentioning that I think I have a fix for the issue we’re to discuss tomorrow. We need the Stylesheets repo!
Elisa, worried sick and anxiously awaiting word from GitHub. -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/
participants (1)
-
Elisa Beshero-Bondar