Establish and include Pagure migration documentation

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This commit is contained in:
Akashdeep Dhar 2025-09-15 11:31:04 +05:30
commit 289504990d
2 changed files with 87 additions and 0 deletions

View file

@ -6,5 +6,6 @@
* Admin Documentation
** xref:creating_a_new_org.adoc[Creating a new Organization]
** xref:creating_a_new_team.adoc[Creating a new Team]
** xref:migration/pagure.adoc[Migrating from Pagure]
* Known Issues
** xref:known_issue_cannot_create_user.adoc[Unable to Log in - "Cannot Create Account"]

View file

@ -0,0 +1,86 @@
= Migrating Repository from Pagure
Akashdeep Dhar
:revnumber: F42
:revdate: 2025-09-15
:category: Administration
:page-aliases: pagure.adoc
:imagesdir: ../../assets/images
== Introduction
With the introduction of Forgejo-based Fedora Forge in Fedora Infrastructure
and the imminent decommissioning of the Pagure service, it is strongly
recommended for the repositories housed over there to be moved over 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, migrating repositories having them would require a workaround of
creating two destination repositories - one publicly accessible and one
privately restricted, to ensure the confidentiality of those issue tickets.
[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 Pagure and take note of the URL of the source repository.
image:migration_pagure_01.png[]
2. Click on your portrait and then navigate to the user settings.
image:migration_pagure_02.png[]
3. Provide your credentials to log into Pagure if required to do so.
image:migration_pagure_03.png[]
4. In the API Keys section, click on the *Create new API key* button.
image:migration_pagure_04.png[]
5. Select all necessary ACLs before clicking on the *Create* button.
image:migration_pagure_05.png[]
6. Copy the API key thus created and keep it aside safely for use.
image:migration_pagure_06.png[]
7. Log into Forge and navigate to the destination namespace.
image:migration_pagure_07.png[]
8. Click on the *New migration* button to begin the migration process.
image:migration_pagure_08.png[]
9. Click on the *Pagure* button at the bottom of the page.
image:migration_pagure_09.png[]
10. Fill in the information taken from the source repository carefully.
image:migration_pagure_10.png[]
11. Leave the token empty and click on the *Migrate repository* button.
image:migration_pagure_11.png[]
12. This should create a repository with the publicly accessible data.
image:migration_pagure_12.png[]
13. Return to the *New migration* page and click on the *Pagure* button.
image:migration_pagure_09.png[]
14. Fill the name and token, visibility appropriately before starting.
image:migration_pagure_13.png[]
15. This should create a repository with the privately restricted data.
image:migration_pagure_14.png[]