Infrastructure/arc
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Add conclusions to Pagure2Gitlab investigation

Browse source 
This adds conclusion to the investigation and updates few things in GitLab API
investigation that are related to that.

Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2023-01-25 15:26:23 +01:00 • committed by zlopez
parent 1552736e56
commit f99f7e1d56
2 changed files with 45 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/pagure2gitlab/gitlab.rst
View file

@ -84,6 +84,18 @@ I tested this on `ARC project ticket <https://pagure.io/fedora-infra/arc/issue/5
"body": "(This comment was added by [t0xic0der](https://accounts.fedoraproject.org/user/t0xic0der/))\n\nHere's a sample comment as you requested @zlopez."
}
The information about GitLab account could be added as well. This could be obtained by using
`users API call <https://docs.gitlab.com/ee/api/users.html>`_ with `mail` as parameter. If the
user is found it will username of the user on GitLab. The final requests could look like this:
.. code-block:: json
{
"created_at": "2023-01-19T12:59:59Z",
"body": "(This comment was added by @t0xic0der [FAS](https://accounts.fedoraproject.org/user/t0xic0der/))\n\nHere's a sample comment as you requested @zlopez."
}
Importing pull requests
-----------------------
@ -98,13 +110,18 @@ the options that could be leveraged by the user for migration:
This option makes the migration process much easier, but we will not have any already
existing pull request in GitLab at all.
2. Migrate forks to GitLab as well
2. Merge all the pull requests before migration
This is the best option for migration. Migration of the merged code is easy and there wouldn't
be any information loss when migrating.
3. Migrate forks to GitLab as well
This will allow us to create pull requests from migrated forks of the original repository.
But this option means migrating plenty of git repositories, just to open the pull requests.
If this option is chosen, I'm recommending to only limit this to open pull requests on Pagure.
3. Create branches on migrated repository
4. Create branches on migrated repository
It's easy to open pull request from branch on the same repository, but this will mean that
tool will need to go through all the forks, add them as remotes and then add those as