GitHub/Archival Process: Difference between revisions
Cknowles-moz (talk | contribs) (Created page with "= Archival Process = Occasionally GHE Admins will be traversing orgs looking for inactive repos. Currently, repos with no activity since April 1 2019 will be archived. Pa...") |
Cknowles-moz (talk | contribs) (updating so this isn't around just the 2022 archiving, but more apropos for the ongoing archive work.) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Archival Process = | = Archival Process = | ||
You have likely arrived here by following a link in an archived repository under Mozilla control. | |||
Occasionally GitHub Enterprise (GHE) Admins will audit GitHub organizations (orgs) looking for inactive repositories (repos). Currently, the threshold for inactive repos is 3 years without any commits or writes to the repo. | |||
Archiving the repo will make it read only. | Part of the archive process will create labels with a link to this page, explaining the change. Archiving the repo will make it read only. Per GitHub best practices, we will be closing all open issues and PRs (after labeling them as having been closed as part of archiving). | ||
Anyone who is subscribed to the repository, or to issues/PRs in the repo, may receive emails due to this archiving activity. | |||
The archiving process is fully reversible. An archived repo that needs to be read-write can be easily un-archived, including restoring the PR's and open issues at the time of archiving. To request a repo to be un-archived, please file a bug at the link below with the repo's name and a brief description of how it is still in use. Note that administrators of the repo can manually do the un-archiving themselves via the settings page. | |||
The archiving process is reversible | |||
https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration | https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration | ||
If you have any questions or concerns, please reach out to ghe-admins@mozilla.com or #github-admin on matrix. | If you have any questions or concerns, please reach out to ghe-admins@mozilla.com or #github-admin on matrix. | ||
Latest revision as of 21:11, 15 July 2024
Archival Process
You have likely arrived here by following a link in an archived repository under Mozilla control.
Occasionally GitHub Enterprise (GHE) Admins will audit GitHub organizations (orgs) looking for inactive repositories (repos). Currently, the threshold for inactive repos is 3 years without any commits or writes to the repo.
Part of the archive process will create labels with a link to this page, explaining the change. Archiving the repo will make it read only. Per GitHub best practices, we will be closing all open issues and PRs (after labeling them as having been closed as part of archiving).
Anyone who is subscribed to the repository, or to issues/PRs in the repo, may receive emails due to this archiving activity.
The archiving process is fully reversible. An archived repo that needs to be read-write can be easily un-archived, including restoring the PR's and open issues at the time of archiving. To request a repo to be un-archived, please file a bug at the link below with the repo's name and a brief description of how it is still in use. Note that administrators of the repo can manually do the un-archiving themselves via the settings page.
https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration
If you have any questions or concerns, please reach out to ghe-admins@mozilla.com or #github-admin on matrix.