Skip to content

Forking a project to a namespace with lower visibility

Bob Van Landuyt requested to merge bvl-fork-public-project-to-private-namespace into master

What does this MR do?

This MR picks the visibility level when forking a project based on the target namespace: It will pick the lowest visibility level of both. This means it is now possible to fork a public project into a private namespace.

If the picked visibility level is restricted, we will fall back to PRIVATE.

Are there points in the code the reviewer needs to double check?

I changed the fallback from highest available level to lowest available level (or private).

I believe this is more acceptable: If a project was internal, and internal is restricted, we might not want the project to become public by default. This way it drops down to a more restrictive level, and an admin can change it later if desired.

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [z] Tests added for this feature/bug
  • Review
    • Has been reviewed by Backend

What are the relevant issue numbers?

Closes #40022 (closed)

Edited by Bob Van Landuyt

Merge request reports