Details
-
Task
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
CP: ready for planning, DevOps Sprint 134
-
FOLIO DevOps
Description
Document the method for archiving repositories as deprecated.
There are various repositories that are no longer in use. Some have already been partially marked, in different ways, as being deprecated. Some have been "archived" as read-only at GitHub, but no statement in the README or "About" text. Some have been renamed, but not archived.
Follow https://dev.folio.org/faqs/how-to-archive-repository/
(Note that if really must be renamed, then that is very different and has many ramifications.)
This enables people to know at a glance, and enables any maintenance scripts that process all repositories to avoid these.
Please add Comments at FOLIO-1838 for other repositories that we know should be archived. Please close any of its open pull-requests. Note that archiving does still enable the repository to be re-enabled later if needed.
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-1838 Follow the documented procedure to fully deprecate existing old repositories
-
- Open
-
- relates to
-
FOLIO-618 clean-up folio organization
-
- Open
-