|
|
[[_TOC_]]
|
|
|
|
|
|
# Import done by Gitlab admins
|
|
|
# Importing/moving a project from Github to Gitlab
|
|
|
|
|
|
As the person who wants to migrate a repository to Gitlab:
|
|
|
This imports both the git repo and the full list of issues. It's a good option if you want the issue tracking to happen on CiviCRM's Gitlab.
|
|
|
|
|
|
* Request a new extension project space, as documented in [how to request a new extension project on gitlab](how to request a new extension project on gitlab)
|
|
|
* Send a [personal Github token](https://github.com/settings/tokens) to the admin
|
|
|
|
|
|
As the Gitlab admin:
|
|
|
|
|
|
* Impersonate the `robot` account (go to Admin > Users, then filter by username)
|
|
|
* Go to the [extensions](https://lab.civicrm.org/extensions) group, and create a new project
|
|
|
* In Github, create a new [personal Github token](https://github.com/settings/tokens)
|
|
|
* In Gitlab, create a new project under your own personal project space (ex: lab.civicrm.org/janedoe/myextension)
|
|
|
* Go to the Import tab, then select Github
|
|
|
* Enter the access token
|
|
|
* Careful to only import the given project (do not click that tempting "import all" button), and import directly to the 'extensions' namespace (default is under the user's space)
|
|
|
* Careful to only import the given project (do not click that tempting "import all" button)
|
|
|
|
|
|
# Import yourself
|
|
|
Once that is done:
|
|
|
|
|
|
(this has not been tested)
|
|
|
* Request a new extension project space, as documented in [how to request a new extension project on gitlab](how to request a new extension project on gitlab)
|
|
|
* Mention that you want that we migrate the project under your personal space (and please provide the link/URL to that project).
|
|
|
|
|
|
The admins will then move the project directly under https://lab.civicrm.org/extensions |
|
|
\ No newline at end of file |