TEI Stylesheets Restored (whew!)

Elisa Beshero-Bondar

2 Nov 2017 2 Nov '17

5:40 a.m.

Dear Council— I am relieved to report that GitHub Support promptly restored our Stylesheets repo, Issues and all(!) I’m forwarding their message. Meanwhile, I’m taking this as an extreme note of caution about working with forks—I consider myself a pretty experienced GitHub user, and that happened a little too fast and easily for comfort. Elisa -- 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/

...

Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/ https://github.com/TEIC/Stylesheets/ , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

Show replies by date

Magdalena Turska

2 Nov 2 Nov

10:14 a.m.

New subject: [tei-council] TEI Stylesheets Restored (whew!)

Phew, Elisa, I bet you've had a stressful evening! Glad everything worked out fine in the end and yes, caution is our middle name. If that cheers you up, I think we all have committed one time or another the famous `rm -rf` as root (or something similarly stupid) :-) Best, Magdalena On 2 November 2017 at 05:40, Elisa Beshero-Bondar wrote:

...

Dear Council— I am relieved to report that GitHub Support promptly restored our Stylesheets repo, Issues and all(!) I’m forwarding their message.

Meanwhile, I’m taking this as an extreme note of caution about working with forks—I consider myself a pretty experienced GitHub user, and that happened a little too fast and easily for comfort.

Elisa -- 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/

...
Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets <https://github.com/TEIC/Stylesheets

Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/ <https://github.com/TEIC/ Stylesheets/> , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Peter Stadler

10:55 a.m.

New subject: [tei-council] TEI Stylesheets Restored (whew!)

Wow, it could have been worse! I was just looking at the Stylesheets repo and it seems to work for me – at least I could pull … But on the GitHub page I do not see any settings. It seems all(?) rights have been transferred to you? or the TEIC maintainers? I think James once set all repo settings to read/write for every Council member. Second, I could not add the Stylesheets repo back to the pinned repositories on the Github TEIC page. But this is more or less cosmetics, the repo and the issues seem to be there! Cheers Peter

...

Am 02.11.2017 um 05:40 schrieb Elisa Beshero-Bondar :

Dear Council— I am relieved to report that GitHub Support promptly restored our Stylesheets repo, Issues and all(!) I’m forwarding their message.

Meanwhile, I’m taking this as an extreme note of caution about working with forks—I consider myself a pretty experienced GitHub user, and that happened a little too fast and easily for comfort.

Elisa -- 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/

...
Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/ https://github.com/TEIC/Stylesheets/ , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Peter Stadler

11:46 a.m.

New subject: [tei-council] TEI Stylesheets Restored (whew!)

Update: I was just trying to push to some (my) branch of the Stylesheets repo and it failed: "You may not have permission to access TEI-Stylesheets. Check Preferences to make sure you’re still logged in.“ Indeed, there seems to be a permission issue … Peter

...

Am 02.11.2017 um 10:55 schrieb Peter Stadler :

Wow, it could have been worse!

I was just looking at the Stylesheets repo and it seems to work for me – at least I could pull … But on the GitHub page I do not see any settings. It seems all(?) rights have been transferred to you? or the TEIC maintainers? I think James once set all repo settings to read/write for every Council member. Second, I could not add the Stylesheets repo back to the pinned repositories on the Github TEIC page.

But this is more or less cosmetics, the repo and the issues seem to be there!

Cheers Peter

...
Am 02.11.2017 um 05:40 schrieb Elisa Beshero-Bondar :

Dear Council— I am relieved to report that GitHub Support promptly restored our Stylesheets repo, Issues and all(!) I’m forwarding their message.

Meanwhile, I’m taking this as an extreme note of caution about working with forks—I consider myself a pretty experienced GitHub user, and that happened a little too fast and easily for comfort.

Elisa -- 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/

...
Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/ https://github.com/TEIC/Stylesheets/ , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Elisa Beshero-Bondar

9 Nov 9 Nov

8:51 p.m.

New subject: [tei-council] TEI Stylesheets Restored (whew!)

Peter— I’m looking at the Permissions on the Stylesheets repo, and I don’t see that I am owner of anything there. (How can we determine this?) What I *do* see on the Settings page is that Technical Council has “Admin” rights—that’s all of us. But there is a “Stylesheets” team of presumably 7 members that has “Write” access. When I click on the “7 members” link, I get a 404 error, so I wonder if this is the source of the problem you’re describing? The web repo has a long list of branches, including peterstadler-fix-multiple-schemaSpecs—is that the one you couldn’t push to? I *do* see the Stylesheets as one of the TEI repositories here: https://github.com/TEIC https://github.com/TEIC When you say it’s missing—is it from a different page? Elisa -- 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/

...

On Nov 2, 2017, at 6:46 AM, Peter Stadler wrote:

Update: I was just trying to push to some (my) branch of the Stylesheets repo and it failed: "You may not have permission to access TEI-Stylesheets. Check Preferences to make sure you’re still logged in.“

Indeed, there seems to be a permission issue …

Peter

...
Am 02.11.2017 um 10:55 schrieb Peter Stadler :

Wow, it could have been worse!

I was just looking at the Stylesheets repo and it seems to work for me – at least I could pull … But on the GitHub page I do not see any settings. It seems all(?) rights have been transferred to you? or the TEIC maintainers? I think James once set all repo settings to read/write for every Council member. Second, I could not add the Stylesheets repo back to the pinned repositories on the Github TEIC page.

But this is more or less cosmetics, the repo and the issues seem to be there!

Cheers Peter

...
Am 02.11.2017 um 05:40 schrieb Elisa Beshero-Bondar :

Dear Council— I am relieved to report that GitHub Support promptly restored our Stylesheets repo, Issues and all(!) I’m forwarding their message.

Meanwhile, I’m taking this as an extreme note of caution about working with forks—I consider myself a pretty experienced GitHub user, and that happened a little too fast and easily for comfort.

Elisa -- 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/

...
Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/ https://github.com/TEIC/Stylesheets/ , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Peter Stadler

3 Nov 3 Nov

12:47 p.m.

New subject: [tei-council] TEI Stylesheets Restored (whew!)

Dear GitHub support, thanks for restoring our repo at https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“. Is it possible to get those links working again or do we have to re-add them manually? Many thanks Peter

...

Am 02.11.2017 um 05:40 schrieb Elisa Beshero-Bondar :

...
Begin forwarded message:

From: "lesley (GitHub Staff)" Subject: Re: help! Deleted a repo origin when I meant to delete my own fork Date: November 2, 2017 at 12:35:47 AM EDT To: Elisa Beshero-Bondar

Hi Elisa,

Repository deletions from our servers are processed quite promptly, but luckily in this instance your repository was still available for recovery. Please bear in mind that this will not always be the case.

I've gone ahead and processed the restore for you, so you should see your repository reappear shortly;

https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets Let me know if you need anything else!

All the best, Lesley GitHub Support

I was attempting to delete my fork of the TEI Stylesheets repository, located at https://github.com/TEIC/Stylesheets/https://github.com/TEIC/Stylesheets/ , but I deleted the remote origin instead! This is terrible because the TEI community depends on this repo, and we need to restore it ASAP. The repository is years old and has issues on it that we rely on track and correct TEI code. We need to restore the entire repository as it was prior to my deleting it--around 11:30pm EST on November 1, 2017.

Stacey Burns (GitHub Staff)

2:35 p.m.

New subject: [tei-council] help! Deleted a repo origin when I meant to delete my own fork

Hi Peter, I'm afraid this is expected behaviour when we restore repositories. The files that were previously uploaded aren't restored with the repository. We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release. Cheers Stacey

...

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

Peter Stadler

4:19 p.m.

New subject: [tei-council] Fwd: help! Deleted a repo origin when I meant to delete my own fork

So, I updated the current release manually. Do you think we should do this for the others, as well?! Cheers Peter

...

Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler Kopie: TEI Council

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

Elisa Beshero-Bondar

9 Nov 9 Nov

8:39 p.m.

New subject: [tei-council] Fwd: help! Deleted a repo origin when I meant to delete my own fork

Well, I’d say we want those links--Sounds like something you should set me to work on!!! I ought to take responsibility for it since it was my great misstep that caused the trouble. but if anyone is willing to help me, I’d be grateful… Elisa -- 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/

...

On Nov 3, 2017, at 11:19 AM, Peter Stadler wrote:

So, I updated the current release manually. Do you think we should do this for the others, as well?!

Cheers Peter

...
Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler Kopie: TEI Council

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Elisa Beshero-Bondar

8:57 p.m.

New subject: [tei-council] Fwd: help! Deleted a repo origin when I meant to delete my own fork

Peter and everyone (cc: Martin) — I *do* see Settings on the web Stylesheets GitHub repo, and I also see that I have capacity to “Transfer Ownership”. I don’t know whether I had this capacity before, but could each of you check and see whether you have access to this? https://github.com/TEIC/Stylesheets/settings https://github.com/TEIC/Stylesheets/settings I definitely shouldn’t be the only one who can see this, and we ought to get these settings back to their state prior to the near-catastrophe of last week… Thanks, Elisa -- 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/

...

On Nov 3, 2017, at 11:19 AM, Peter Stadler wrote:

So, I updated the current release manually. Do you think we should do this for the others, as well?!

Cheers Peter

...
Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler Kopie: TEI Council

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Martin Holmes

10:49 p.m.

New subject: [tei-council] Fwd: help! Deleted a repo origin when I meant to delete my own fork

I have permission to Transfer, Archive and Delete the repo. It would be nice if we could turn off Transfer and Delete. But it is all clearly marked "Danger Zone". :-) On 2017-11-09 11:57 AM, Elisa Beshero-Bondar wrote:

...

Peter and everyone (cc: Martin) — I *do* see Settings on the web Stylesheets GitHub repo, and I also see that I have capacity to “Transfer Ownership”. I don’t know whether I had this capacity before, but could each of you check and see whether you have access to this? https://github.com/TEIC/Stylesheets/settings I definitely shouldn’t be the only one who can see this, and we ought to get these settings back to their state prior to the near-catastrophe of last week…

Thanks, Elisa

-- 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

...
On Nov 3, 2017, at 11:19 AM, Peter Stadler mailto:stadler@edirom.de> wrote:

So, I updated the current release manually. Do you think we should do this for the others, as well?!

Cheers Peter

...
Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" mailto:support@github.com> Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler mailto:stadler@edirom.de> Kopie: TEI Council mailto:tei-council@lists.tei-c.org>

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

-- tei-council mailing list tei-council@lists.tei-c.org mailto:tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Peter Stadler

10 Nov 10 Nov

10:51 a.m.

New subject: [tei-council] help! Deleted a repo origin when I meant to delete my own fork

Yes I do see the settings page and can change things (including the danger part). This wasn’t the case a few days ago but I believe James adjusted the permissions (for every Council member) during the last Stylesheets conference call on 2 Nov. Regarding the releases, I was just deleting the old binary and uploading from Subversion manually. This could probably be scripted with the GitHub API but I haven’t looked into that. Best Peter

...

Am 09.11.2017 um 22:49 schrieb Martin Holmes :

I have permission to Transfer, Archive and Delete the repo. It would be nice if we could turn off Transfer and Delete. But it is all clearly marked "Danger Zone". :-)

On 2017-11-09 11:57 AM, Elisa Beshero-Bondar wrote:

...
Peter and everyone (cc: Martin) — I *do* see Settings on the web Stylesheets GitHub repo, and I also see that I have capacity to “Transfer Ownership”. I don’t know whether I had this capacity before, but could each of you check and see whether you have access to this? https://github.com/TEIC/Stylesheets/settings I definitely shouldn’t be the only one who can see this, and we ought to get these settings back to their state prior to the near-catastrophe of last week… Thanks, Elisa -- 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

...
On Nov 3, 2017, at 11:19 AM, Peter Stadler mailto:stadler@edirom.de> wrote:

So, I updated the current release manually. Do you think we should do this for the others, as well?!

Cheers Peter

...
Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" mailto:support@github.com> Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler mailto:stadler@edirom.de> Kopie: TEI Council mailto:tei-council@lists.tei-c.org>

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

-- tei-council mailing list tei-council@lists.tei-c.org mailto:tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Elisa Beshero-Bondar

9 Nov 9 Nov

9:08 p.m.

New subject: [tei-council] Fwd: help! Deleted a repo origin when I meant to delete my own fork

One more question: If I wanted to go through the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases ) and restore access to each of the previous Release files (as Peter, you just did for the current release), what’s the best way to proceed? (I’m happy to work on this when I see you all in a few days.) Elisa -- 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/

...

On Nov 3, 2017, at 11:19 AM, Peter Stadler wrote:

So, I updated the current release manually. Do you think we should do this for the others, as well?!

Cheers Peter

...
Anfang der weitergeleiteten Nachricht:

Von: "Stacey Burns (GitHub Staff)" Betreff: Aw: help! Deleted a repo origin when I meant to delete my own fork Datum: 3. November 2017 um 14:35:48 MEZ An: Peter Stadler Kopie: TEI Council

Hi Peter,

I'm afraid this is expected behaviour when we restore repositories.

The files that were previously uploaded aren't restored with the repository.

We do have an issue opened internally to investigate ways to improve the current behaviour but in the meantime, the files will need to be uploaded again to the release.

Cheers Stacey

Dear GitHub support,

thanks for restoring our repo at https://github.com/TEIC/Stylesheets https://github.com/TEIC/Stylesheets. We are back and running but I just discovered that all(?) download links on the release page (https://github.com/TEIC/Stylesheets/releases https://github.com/TEIC/Stylesheets/releases) to attached binaries do not work, see e.g. https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... https://github.com/TEIC/Stylesheets/releases/download/v7.43.0/tei-xsl-7.43.0... – instead returning a nice API error saying "The specified key does not exist“.

Is it possible to get those links working again or do we have to re-add them manually?

Many thanks Peter

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

2562

Age (days ago)

2570

Last active (days ago)

List overview

Download

12 comments

5 participants

participants (5)

Elisa Beshero-Bondar
Magdalena Turska
Martin Holmes
Peter Stadler
Stacey Burns (GitHub Staff)