- Introduced in GitLab 15.9, Rake task no longer automatically creates namespaces or groups that don’t exist.
- Requirement for Maintainer role instead of Developer role introduced in GitLab 16.0 and backported to GitLab 15.11.1 and GitLab 15.10.5.
To retrieve and import GitHub repositories, you need a GitHub personal access token. A username should be passed as the second argument to the Rake task, which becomes the owner of the project. You can resume an import with the same command.
Bear in mind that the syntax is very specific. Remove any spaces in the argument block and
before/after the brackets. Also, some shells (for example, Zsh) can interpret the open/close brackets
) separately. You may want to either escape the brackets or use double quotes.
You can only import repositories that are in the namespace of the owner of the GitHub personal access token being used to import. For more information, see issue 424105.
- At least the Maintainer role on the destination group to import to.
If the GitHub rate limit is reached while
importing, the importing process waits (
sleep()) until it can continue importing.
To import a project from the list of your GitHub projects available:
# Omnibus installations sudo gitlab-rake "import:github[access_token,root,foo/bar]" # Installations from source bundle exec rake "import:github[access_token,root,foo/bar]" RAILS_ENV=production
In this case,
access_token is your GitHub personal access token,
is your GitLab username, and
foo/bar is the new GitLab namespace/project
created from your GitHub project. Subgroups are also possible:
To import a specific GitHub project (named
# Omnibus installations sudo gitlab-rake "import:github[access_token,root,foo/bar,foo/github_repo]" # Installations from source bundle exec rake "import:github[access_token,root,foo/bar,foo/github_repo]" RAILS_ENV=production