diff options
Diffstat (limited to 'doc/user/project/repository/forking_workflow.md')
| -rw-r--r-- | doc/user/project/repository/forking_workflow.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/user/project/repository/forking_workflow.md b/doc/user/project/repository/forking_workflow.md index 690cf4a04a5..85414a55e81 100644 --- a/doc/user/project/repository/forking_workflow.md +++ b/doc/user/project/repository/forking_workflow.md @@ -101,7 +101,7 @@ an `upstream` remote repository for your fork: A fork can be configured as a mirror of the upstream if all these conditions are met: -1. Your subscription is **(PREMIUM)** or a higher tier. +1. Your subscription is **Premium** or higher. 1. You create all changes in branches (not `main`). 1. You do not work on [merge requests for confidential issues](../merge_requests/confidential.md), which requires changes to `main`. @@ -132,6 +132,12 @@ changes are added to the repository and branch you're merging into. You can unlink your fork from its upstream project in the [advanced settings](../settings/index.md#remove-a-fork-relationship). +If you unlink a fork in this way and if [pool repositories](../../../development/git_object_deduplication.md#pool-repositories) are used, all objects are +copied from the pool into the fork. + +After this copy is complete, the relationship is broken and the fork becomes an independent project. From this point, any updates to objects in the pool are +not propagated to the project that was previously a fork. + ## Related topics - GitLab blog post: [Keep your fork up to date with its origin](https://about.gitlab.com/blog/2016/12/01/how-to-keep-your-fork-up-to-date-with-its-origin/) |