Archiving
Open source repositories don't necessarily stay under active development forever. If you're thinking about making your repository read only or deleting it, you should instead archive it.
For more general guidance for deprecating an open source project, see go/oss-guides/deprecation-checklist.
Follow these steps to archive your repository:
- Update the
READMEto indicate to users that the repository is no longer being maintained - Archive the repository using GitHub's archive feature
- (Optional) Transfer the repository to googlearchive if you want to keep your organization uncluttered. This can be done at go/github/archive, and will also archive the repository using GitHub's archiving feature if you didn't already do so in the previous step.
Using GitHub's archiving feature means that all aspects of the repository will become read-only, including code, pull requests, issues, wiki, and more. Please read GitHub's documentation on archiving repositories before archiving a repository.
We maintain a dedicated organization for archived Google repositories and you can request that your repository be transferred to it. Once it has been transferred, you will no longer be able to make modifications to the repository, and will not have permissions to do so. To request the transfer, please see the instructions at go/github-docs/transfer.
Unarchiving
If you've archived a repository by moving it into Google Archive, file a bug asking for it to be moved to a different organization (make sure that the organization administrator is supportive of this move). If you've archived a repository by using GitHub's archiving functionality, you may unarchive it by following GitHub's instructions.
Transferring
For instructions on how and when to transfer a repository, see go/github-docs/transfer.
Disabling features of GitHub repositories {disable}
If you manage contributions elsewhere, you can disable github features like issues and pull requests. For more information, see go/github-docs/disable-features.