Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
You must enable private mode if your GitHub Enterprise Server instance is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over git://. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "Using built-in authentication."
Warning: If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication, even if the pull request is in a private repository, or if private mode is enabled. To keep sensitive images private, serve them from a private network or server that requires authentication.
With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to your GitHub Enterprise Server instance) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "Allowing admins to enable anonymous Git read access to public repositories."
- From a GitHub Enterprise Server administrative account, click in the upper-right corner of any page.
- In the left sidebar, click Management Console.
- In the left sidebar, click Privacy.
- Select Private mode.
- Under the left sidebar, click Save settings.
- Wait for the configuration run to complete.