Private forks are typically private because they contain confidential changes. We should prevent any developer from exposing those changes by opening a public merge request ### Further details GitLab wants to be able to fix security issues on `gitlab-ce` on GitLab.com rather than using a second private instance. Initially we will use a private fork (e.g `secure-ce`). When engineers are working on security fixes on `secure-ce` we need to make sure changes aren't accidentally merged into `gitlab-ce` ### Proposal Only allow maintainers to open merge requests from private projects to public projects. ### Links / references <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->