Gitea importer not visible on page New project/Import project

How to Use GitLab Migrations
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

I am trying to import a project with its issues from a private Gitea instance into a private project on GitLab.com. In contrary to the documentation there seems to be Gitea importer available.

Migrate from Gitea | GitLab Docs says:

The Gitea import source is enabled by default on GitLab.com.

On https://lab.las3.de/gitlab/help/workflow/importing/import_projects_from_gitea.md I found a screenshot that definitely depicts a dedicated button for importing from Gitea.

On GitLab.com it looks like this instead with less many buttons:

b70637a4bfa77d8f
b70637a4bfa77d8f1393×476 29.6 KB

I tried both to import into my personal free account as well as into a group with the [OSS] Ultimate SaaS Plan.

Steps to reproduce

  1. login to GitLab.com
  2. go to https://gitlab.com/projects/new#import_project

Configuration

GitLab.com

Versions

Please select whether options apply, and add the version information.

Versions

2

There’s an active incident going on, more in this incident and follow-up incident

Edit 2024-07-22: Added 2nd incident URL for clarity.

2 Likes
3

Thanks @dnsmichi for the reply but the problem is not yet solved for me :pensive:

The GitLab status incident is now green and marked as operational since July 8 but my project import page looks the same as before. I verified that’s exactly the same list of 5 import sources to choose from without mentioning Gitea.

Is it already broken again or is there something else that’s wrong?

4

Yep, after the July 8 one, another appeared on July 11 which still isn’t resolved: GitLab System Status

1 Like
5

You might want to try this trick. It’s easy to set up a Gitlab self-hosted instance.

github → import on private gitlab → export → import on gitlab.com roundtrip that might just work.

1 Like
6

I didn’t have a private GitLab instance at hand. But because the issue seems to permit without anyone taking care of the Gitea import service I went to one of my clients and used their private GitLab instance to use the trick.

It actually worked but the process is not satisfactory. :pensive:

1 Like
8

You may want to read or comment on this issue. I guess there’s something wrong at architectural level.

9

Thanks for the link, you saved my day.

1 Like