t0xic0der/forge-documentation
1
0
Fork 0
forked from forge/documentation
Code Pull requests Activity

Establish and include GitLab migration documentation

Browse source 
Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This commit is contained in:
Akashdeep Dhar 2025-09-16 11:28:06 +05:30 • committed by Ryan Lerch
commit 11f67c20db
2 changed files with 74 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
modules/ROOT/nav.adoc
View file

@ -8,5 +8,6 @@
** xref:creating_a_new_team.adoc[Creating a new Team]
** xref:migration/pagure.adoc[Migrating from Pagure]
** xref:migration/github.adoc[Migrating from GitHub]
** xref:migration/gitlab.adoc[Migration from GitLab]
* Known Issues
** xref:known_issue_cannot_create_user.adoc[Unable to Log in - "Cannot Create Account"]

73
modules/ROOT/pages/migration/gitlab.adoc Normal file
View file

@ -0,0 +1,73 @@
= Migrating Repository from GitLab
Akashdeep Dhar
:revnumber: F42
:revdate: 2025-09-16
:category: Administration
:page-aliases: gitlab.adoc
:imagesdir: ../../assets/images
== Introduction
With the introduction of Forgejo-based Forge in Fedora Infrastructure,
maintainers of repositories involved with the Fedora Project's offerings are
advised to move their repositories from GitLab to the newly introduced
platform. This documentation covers the steps required to achieve this goal.
[WARNING]
As the Forgejo-based Fedora Forge houses only those repositories that are
instrumental in the development, testing, maintenance and operating of the
Fedora Project's offering of Fedora Linux, please use this for those
repositories only -- and not for any other personal repositories.
[WARNING]
As Forgejo does not support the creation of privately restricted issue tickets
at this time, please take extra care while migrating those away from the source
namespace on GitLab to ensure that confidential information contained in those
issue tickets are not accidentally released out in the process.
[NOTE]
This guide assumes that you have the necessary privileges to be able to create
a repository under the sought namespace in Fedora Forge. If that is not the
case, please consult a member from the said subproject or SIG for the required
privileges, or the Fedora Infrastructure team if you are involved.
[NOTE]
We recommend migrating your other personal repositories present on Pagure over
to Codeberg, which is also based on Forgejo and supports native migration of
repository contents, issue tickets and pull requests from Pagure using the
instructions provided here -- with some minor changes here and there.
== Steps
1. Log into GitLab and take note of the URL of the source repository.
image:migration_gitlab_01.png[]
2. Head over to the *Settings* > *Access tokens* page from the extended sidebar.
image:migration_gitlab_02.png[]
3. Click on the *Add new token* button on the first section.
image:migration_gitlab_03.png[]
4. Fill in the information and ACLs before clicking on the *Create* button.
image:migration_gitlab_04.png[]
5. Copy the personal access token and keep it aside safely for use.
image:migration_gitlab_05.png[]
6. Log into Forge and navigate to the destination namespace.
image:migration_gitlab_06.png[]
7. Click on the *New migration* button to begin the migration process.
image:migration_gitlab_07.png[]
8. Click on the *GitLab* button at the top of the page.
image:migration_gitlab_08.png[]
9. Fill in the information taken from the source repository carefully.
image:migration_gitlab_09.png[]
10. Click on the *Migrate repository* button and wait until it completes.
image:migration_gitlab_10.png[]
11. Verify the successful migration of the repository once it is done.
image:migration_gitlab_11.png[]