summaryrefslogtreecommitdiff
path: root/doc/tutorials/move_personal_project_to_a_group.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tutorials/move_personal_project_to_a_group.md')
-rw-r--r--doc/tutorials/move_personal_project_to_a_group.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tutorials/move_personal_project_to_a_group.md b/doc/tutorials/move_personal_project_to_a_group.md
index 1431dc48d99..e3ab1e8fbd8 100644
--- a/doc/tutorials/move_personal_project_to_a_group.md
+++ b/doc/tutorials/move_personal_project_to_a_group.md
@@ -53,7 +53,7 @@ If you don't have a group, create one:
Before you move your project to a group:
- You must have the Owner role for the project.
-- Remove any [container images](../user/packages/container_registry/index.md#known-issues)
+- Remove any [container images](../user/packages/container_registry/index.md#move-or-rename-container-registry-repositories)
- Remove any npm packages. If you transfer a project to a different root namespace, the project must not contain any npm packages. When you update the path of a user or group, or transfer a subgroup or project, you must remove any npm packages first. You cannot update the root namespace of a project with npm packages. Make sure you update your .npmrc files to follow the naming convention and run npm publish if necessary.
Now you're ready to move your project: