The original issue is: https://gitlab.com/gitlab-org/gitlab/-/issues/24180 Following on from discussion in this merge request: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/41103#note_407478421 We need to do a few things in order to allow for merge requests to be made from confidential issues. Currently, when we fork a project, it matches the visibility of the parent project. If this project is public, we need to make it private before we can use it to create a merge request for the confidential issue. When we change the visibility, we unlink the fork, meaning we can't create a merge request against the parent fork. The reason we originally unforked it was to fix the issue where the visibility was forced onto the children forks. 1. Show a confirmation dialog box when making a merge request from a fork that has a lower visibility than the project. - This lets the user know of potentially exposing code. 1. Remove the unlinking when the visibility changes - Change the copy in the confirmation box when changing visibility to remove mention of unlinking 1. Change the copy in the General settings of the fork to: - > Once removed, the fork relationship cannot be restored and {-you will no longer be able to send merge requests to the source-}{+this project will no longer be able to receive merge requests from the source project+}.