Do not delete gh-pages branch

[zkamvar]

For the @LibraryCarpentry/lc-marcedit-maintainers-workbench and @LibraryCarpentry/lc-marcedit-maintainers,

I have restored the gh-pages branch and rebuild the site.

The gh-pages and md-outputs branches are automatically created by The Workbench to build and deploy the lesson website (see The Automated Workflow for details).

Please do not delete these branches as that will mean that the website cannot be rendered (moreover, in all official repos, the gh-pages branch contains a workflow that protects the branch from old forks merging to it.

You are free to remove any branches that start with legacy/ if you want to clean out content from the former infrastructure. Please let me know if you have any questions and feel free to close this issue any time.

Situation

Six days ago, the gh-pages branch was deleted and 15 hours ago, the scheduled automated build failed because it could not find the gh-pages branch:

Fetch origin/gh-pages
  Running git remote set-branches origin gh-pages
  Running git fetch origin gh-pages
  fatal: couldn't find remote ref gh-pages
  Error in `callr::run("git", c(...), echo_cmd = echo_cmd, echo = echo, error_on_status = error_on_status)`:
  ! System command 'git' failed

I looked back to the activity log and found that it was deleted along with a lot of other branches and was able to restore it.

[jenmawe]

Hi @zkamvar Thanks for doing this work. I saw that our pull requests were having trouble building the site. This explanation is super helpful in terms of what we can delete and not.