From 19ce5baf48b7a850edc749f68e67c77cb9029b6d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michal=20Kone=C4=8Dn=C3=BD?= Date: Mon, 30 Jan 2023 13:22:04 +0100 Subject: [PATCH] Fix the link in conclusion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Michal Konečný --- docs/pagure2gitlab/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pagure2gitlab/index.rst b/docs/pagure2gitlab/index.rst index 89ff1e7..92c465b 100644 --- a/docs/pagure2gitlab/index.rst +++ b/docs/pagure2gitlab/index.rst @@ -64,7 +64,7 @@ but it will add much to complexity of the tool and we need to host it and deploy The main issue with the migration is that all the comments, issues are created by the user that owns the API token, which is made to execute the API calls. This issue is explained -in :ref:`pagure2gitlab/gitlab:Importing ticker` with possible proposed solution. +in :ref:`pagure2gitlab/gitlab:Importing ticket` with possible proposed solution. The user that is using the tool will need to have permissions to create new repositories in the GitLab group, to which the repository will be migrated.