From 3984a5481c956aa4dfbec0c0a689aa54a4f939e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=F0=9F=A4=96=20GitLab=20Bot=20=F0=9F=A4=96?=
<gitlab-bot@gitlab.com>
Date: Fri, 31 May 2024 12:02:52 +0000
Subject: [PATCH 1/3] Remove direct transfer beta status from UI
---
...remove-direct-transfer-beta-status-from-ui.yml | 15 +++++++++++++++
1 file changed, 15 insertions(+)
create mode 100644 data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
diff --git a/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
new file mode 100644
index 0000000000000..074725959ddee
--- /dev/null
+++ b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
@@ -0,0 +1,15 @@
+---
+features:
+ primary:
+ - name: "Remove direct transfer beta status from UI"
+ available_in: []
+ gitlab_com: true
+ documentation_link: 'https://docs.gitlab.com/ee/#amazing'
+ image_url: '/images/unreleased/REPLACE_THIS_WITH_THE_IMAGE_PATH.png'
+ reporter: m_frankiewicz
+ stage: manage
+ categories:
+ - Importers
+ issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/461326'
+ description: |
+ Lorem ipsum [dolor sit amet](#link), consectetur adipisicing elit. Perferendis nisi vitae quod ipsum saepe cumque quia `veritatis`.
--
GitLab
From 443281665ee8386fdf87be017fc6c07c51ee4701 Mon Sep 17 00:00:00 2001
From: Magdalena Frankiewicz <mfrankiewicz@gitlab.com>
Date: Wed, 5 Jun 2024 13:59:32 +0000
Subject: [PATCH 2/3] Update
manage-remove-direct-transfer-beta-status-from-ui.yml
---
...-remove-direct-transfer-beta-status-from-ui.yml | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
index 074725959ddee..c452808b265f0 100644
--- a/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
+++ b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
@@ -1,15 +1,19 @@
---
features:
primary:
- - name: "Remove direct transfer beta status from UI"
- available_in: []
+ - name: "Migrating by direct transfer is now generally available"
+ available_in: [core, premium, ultimate]
gitlab_com: true
- documentation_link: 'https://docs.gitlab.com/ee/#amazing'
+ documentation_link: 'https://docs.gitlab.com/ee/user/group/import/index.html'
image_url: '/images/unreleased/REPLACE_THIS_WITH_THE_IMAGE_PATH.png'
reporter: m_frankiewicz
stage: manage
categories:
- Importers
- issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/461326'
+ issue_url: 'https://gitlab.com/groups/gitlab-org/-/epics/11398'
description: |
- Lorem ipsum [dolor sit amet](#link), consectetur adipisicing elit. Perferendis nisi vitae quod ipsum saepe cumque quia `veritatis`.
+ Migrating GitLab projects by direct transfer is now generally available, bringing an easy to use and automated way of migrating GitLab groups and projects between GitLab instances with network connectivity. To migrate GitLab resources by direct transfer, you can use either UI or the [API](https://docs.gitlab.com/ee/api/bulk_imports.html). UI is intuitive and straightforward, while API gives you more flexibility in terms of choosing resources to be copied.
+
+ Migrating by direct transfer is a major improvement from [migrating groups and projects using file exports](https://docs.gitlab.com/ee/user/project/settings/import_export.html#migrate-projects-by-uploading-an-export-file), because it's automated and efficient, works more reliably with large project, supports migrations with a larger version gap between source and destination instances and offers better insights into the migration process and results. You can read more about it in the following blog post.
+
+ On GitLab.com, migrating by direct transfer is enabled by default. On self-managed GitLab and on Dedicated, an administrator must [enable the feature in application settings](https://docs.gitlab.com/ee/administration/settings/import_and_export_settings.html#enable-migration-of-groups-and-projects-by-direct-transfer).
--
GitLab
From 7ba08a611d8062a4223d5b3a8802b6b3f920e8a5 Mon Sep 17 00:00:00 2001
From: Magdalena Frankiewicz <mfrankiewicz@gitlab.com>
Date: Fri, 7 Jun 2024 11:14:24 +0000
Subject: [PATCH 3/3] Apply reviewer suggestions
---
...ve-direct-transfer-beta-status-from-ui.yml | 20 ++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
index c452808b265f0..cfa9721cefea5 100644
--- a/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
+++ b/data/release_posts/unreleased/manage-remove-direct-transfer-beta-status-from-ui.yml
@@ -12,8 +12,22 @@ features:
- Importers
issue_url: 'https://gitlab.com/groups/gitlab-org/-/epics/11398'
description: |
- Migrating GitLab projects by direct transfer is now generally available, bringing an easy to use and automated way of migrating GitLab groups and projects between GitLab instances with network connectivity. To migrate GitLab resources by direct transfer, you can use either UI or the [API](https://docs.gitlab.com/ee/api/bulk_imports.html). UI is intuitive and straightforward, while API gives you more flexibility in terms of choosing resources to be copied.
+ Migrating GitLab projects by direct transfer is now generally available, bringing an easy to use and automated way of migrating GitLab groups and projects
+ between GitLab instances with network connectivity. To migrate GitLab resources by direct transfer, you can use either:
+
+ - The GitLab UI, which is the intuitive and straightforward method.
+ - The REST [API](https://docs.gitlab.com/ee/api/bulk_imports.html), which is the more flexible method.
- Migrating by direct transfer is a major improvement from [migrating groups and projects using file exports](https://docs.gitlab.com/ee/user/project/settings/import_export.html#migrate-projects-by-uploading-an-export-file), because it's automated and efficient, works more reliably with large project, supports migrations with a larger version gap between source and destination instances and offers better insights into the migration process and results. You can read more about it in the following blog post.
+ Migrating by direct transfer is a major improvement from
+ [migrating groups and projects using file exports](https://docs.gitlab.com/ee/user/project/settings/import_export.html#migrate-projects-by-uploading-an-export-file)
+ because the direct transfer method:
+
+ - Is automated and efficient.
+ - Works more reliably with large projects.
+ - Supports migrations with a larger version gap between source and destination instances.
+ - Offers better insights into the migration process and results.
+
+ Read more about migrating GitLab by direct transfer in the following blog post.
- On GitLab.com, migrating by direct transfer is enabled by default. On self-managed GitLab and on Dedicated, an administrator must [enable the feature in application settings](https://docs.gitlab.com/ee/administration/settings/import_and_export_settings.html#enable-migration-of-groups-and-projects-by-direct-transfer).
+ On GitLab.com, migrating by direct transfer is enabled by default. On self-managed GitLab and on Dedicated, an administrator must
+ [enable the feature in application settings](https://docs.gitlab.com/ee/administration/settings/import_and_export_settings.html#enable-migration-of-groups-and-projects-by-direct-transfer).
--
GitLab