From 03ca338987988d1fab96f385bb87c70227265ed9 Mon Sep 17 00:00:00 2001 From: Alexander Tanayno Date: Wed, 12 Dec 2018 10:46:54 +0000 Subject: add information about how merge requests related to forks are processed the added note describes code from https://gitlab.com/gitlab-org/gitlab-ee/blob/master/lib/gitlab/import_export/merge_request_parser.rb#L15 --- doc/user/project/settings/import_export.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md index f94671fcf87..cb68c9318bc 100644 --- a/doc/user/project/settings/import_export.md +++ b/doc/user/project/settings/import_export.md @@ -24,6 +24,10 @@ > Otherwise, a supplementary comment is left to mention the original author and > the MRs, notes or issues will be owned by the importer. > - Control project Import/Export with the [API](../../../api/project_import_export.md). +> - If an imported project contains merge requests originated from forks, +> then new branches associated with such merge requests will be created +> within a project during the import/export. Thus, the number of branches +> in the exported project could be bigger than in the original project. Existing projects running on any GitLab instance or GitLab.com can be exported with all their related data and be moved into a new GitLab instance. -- cgit v1.2.1