From c2ad17754e189c23dcf8e9495d2b8b52c20eca2c Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Sun, 18 Sep 2016 11:32:01 +0200 Subject: Clarify why GH integration is the preferred importing method --- doc/workflow/importing/import_projects_from_github.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'doc/workflow') diff --git a/doc/workflow/importing/import_projects_from_github.md b/doc/workflow/importing/import_projects_from_github.md index 7e5dd628c94..dd38fe0bc01 100644 --- a/doc/workflow/importing/import_projects_from_github.md +++ b/doc/workflow/importing/import_projects_from_github.md @@ -70,10 +70,11 @@ You can now go on and [select which repositories to import](#select-which-reposi ### Authorize access to your repositories using a personal access token >**Note:** -For a proper author/assignee mapping, the [GitHub integration][gh-integration] -should be used instead of using a [personal access token][gh-token]. If the -GitHub integration is enabled by your GitLab administrator, it should be the -preferred method to import your repositories. +For a proper author/assignee mapping for issues and pull requests, the +[GitHub integration][gh-integration] should be used instead of the +[personal access token][gh-token]. If the GitHub integration is enabled by your +GitLab administrator, it should be the preferred method to import your repositories. +Read more in the [How it works](#how-it-works) section. If you are not using the GitHub integration, you can still perform a one-off authorization with GitHub to grant GitLab access your repositories: -- cgit v1.2.1