GitHub/Archival Process: Difference between revisions
Cknowles-moz (talk | contribs) (Added preamble about where you might have come from.) |
Cknowles-moz (talk | contribs) (not everyone will click, some will be following other methods.) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Archival Process = | = Archival Process = | ||
You | You have likely arrived here by following a link in an archived repository under Mozilla control. | ||
Occasionally GHE Admins will | Occasionally GitHub Enterprise (GHE) Admins will audit GitHub organizations (orgs) looking for inactive repositories (repos). Currently, the threshold for inactive repos is April 1 2019. | ||
Part of the archive process will create labels with a link to this page, explaining the change. | 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. In order to limit the impact of email flooding we will be archiving approximately 100 repos per day. | |||
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. | |||
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 19:54, 14 January 2022
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 April 1 2019.
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. In order to limit the impact of email flooding we will be archiving approximately 100 repos per day.
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.
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.