Add sentence for private repos in Initial Contribution phase.
Compare changes
+ 1
− 1
@@ -121,7 +121,7 @@ All {forgeName} open source project content must be kept in source code reposito
**Move the existing repository.** At the project team's request, the Eclipse Foundation IT Team can move existing source code repositories on xref:resources-github[GitHub] into an organisation managed by the Eclipse Foundation. This is the best option when a project team wants to preserve their repository's status with existing forks, retain existing issues, stars, etc. Note that GitHub does a good job of setting up redirects that will ensure that the project's existing community can find them.
**Move the existing repository.** At the project team's request, the Eclipse Foundation IT Team can move existing source code repositories on xref:resources-github[GitHub] into an organisation managed by the Eclipse Foundation. This is the best option when a project team wants to preserve their repository's status with existing forks, retain existing issues, stars, etc. If the repository is private, it must be made public before the move. Note that GitHub does a good job of setting up redirects that will ensure that the project's existing community can find them.
**Push to a new repository.** At the project team's request, the Eclipse Foundation IT Team can create new source code repositories on either xref:resources-gitlab[GitLab] or xref:resources-github[GitHub] into which the project team can push existing content. This option is best in the case that there is good reason to leave an existing repository in place, or when a project team needs to move an existing private repository into the open. The project team can decide whether or not to push the entire history or just a snapshot from the existing repository. As a best practice, an existing repository that gets "left behind" should be updated to include a pointer to the new repository and marked as _archived_.