We have this issue from nmfs-openscapes repo.
Probably is a good idea to document and iterate as an Openscapes practice how to manage repositories no longer used (?). Below I wrote the link to GitHub documentation which is pretty straigthforward on the steps, but on our side we could think on how to make the decision to archive a repo, what to do with the issues, how to communicate to stakeholders, what to document in the README of the archived repo and so on.
These are the steps I followed to archive the repository.
- Unpublish the old GitHub Pages site.
- README edited to include notes about the current nmfs-openscapes site and repo
- closed issues
- In the 'danger zone' config section, I selected archive repo.

We have this issue from nmfs-openscapes repo.
Probably is a good idea to document and iterate as an Openscapes practice how to manage repositories no longer used (?). Below I wrote the link to GitHub documentation which is pretty straigthforward on the steps, but on our side we could think on how to make the decision to archive a repo, what to do with the issues, how to communicate to stakeholders, what to document in the README of the archived repo and so on.
These are the steps I followed to archive the repository.