Inexhaustive checklist for changing your repository from private (standard) to public

  • Elimitate any private information such as login credentials, passworts, private addresses etc.
  • Add a LICENSE file to your repository
  • Keep your repository name short and memorable
  • Create a user-friendly, introductory README at the root of your repository, which helps researchers unfamiliar with your project to understand what it is about, how the data is structured etc.

Be aware that changing your repository from private to public means that anyone can see and access your data. If you only want to share your repository with selected collaborators, then consider the collaboration option within your repository settings. There you have the option to invite collaborators of your choice. See our FAQ.

A quick security note on unlisting repositories

Besides changing your repositories from private to public, you also have the option to change your repository from listed (standard) to unlisted. Being unlisted means that your repository cannot be found in the Explore view. However, this does not mean that your repository cannot be found! It is not truly hidden from everyone. For example, the repository is accessible via a direct link. So make sure that, even if your repository is unlisted, you do not have an private information in it (see the checklist for changing your repository from private to public for more information).

Achilleas Koutsou edited this page 4 years ago