Migrate from Gitlab to Gitea #5
Labels
No Label
Testing label
Priority: Critical
Priority: High
Priority: Low
Priority: Medium
Release: v0.1
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Feature
Type: Idea
Type: Question
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: athens-school/K3s-cluster#5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that Gitea supports container registry out of the box, it seems like the by-default choice, given how slow Gitlab can be in the current environment.
assigned to @therbron
Currently, the main blocker was the profile heatmap being incomplete. This can be fixed by manually editing Gitea's database (straight forward
action
database) using the/users/{username}/calendar.json
endpoint from Gitlab.A quick and dirty implementation of mass migration has been implemented: https://git.halia.dev/therbron/gitlab_to_gitea/-/tree/shell_rewrite?ref_type=heads
This includes issues, PR, and more.
So far, 2 manual interventions are needed :
The first step of the migration was completed yesterday.
The new organization has been updated with its original picture, and runners have been configured.
The aforementioned issue with SNIR MC has been fixed by rewriting history and backing up space taking directories in another way.
More migration steps will be required, as the initial step only went from docker to docker, not to kubernetes.
Follow up migration steps will add kubernetes deployment (production) and customization of some default Gitea assets.