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

pagure_repository.adoc: Update AsciiDoc syntax

Browse source 
Signed-off-by: Hristo Marinov <hricky@mail.bg>
This commit is contained in:
Hristo Marinov 2025-12-18 14:05:04 +02:00 • committed by Akashdeep Dhar
commit e244527c35
1 changed files with 27 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

55
modules/ROOT/pages/migration/pagure_repository.adoc
View file

@ -2,44 +2,40 @@
[WARNING]
====
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
**DRAFT DOCUMENTATION:**
This documentation is currently in draft form and may not be fully tested and correct.
Please verify all procedures before use and report any issues or inaccuracies.
====
== Purpose
This document outlines the steps required to migrate repositories from Pagure
to Fedora Forge, ensuring proper transfer of repository contents, issue tickets,
and pull requests to the new Forgejo-based platform.
This document outlines the steps required to migrate repositories from Pagure to Fedora Forge, ensuring proper transfer of repository contents, issue tickets, and pull requests to the new Forgejo-based platform.
== Scope
This procedure applies to Fedora Project contributors who need to migrate
repositories from the legacy Pagure service to the new Fedora Forge platform.
This includes subprojects, Special Interest Groups (SIGs), and other official
Fedora Project repositories.
This procedure applies to Fedora Project contributors who need to migrate repositories from the legacy Pagure service to the new Fedora Forge platform.
This includes subprojects, Special Interest Groups (SIGs), and other official Fedora Project repositories.
== Prerequisites
* *Repository Access:* You must have access to the source repository on Pagure
and the necessary privileges to create repositories in the target organization
on Fedora Forge.
* *Organization Permissions:* You must have the ability to create repositories
under the target namespace in Fedora Forge. If you don't have these
privileges, consult a member from the relevant subproject or SIG, or contact
the Fedora Infrastructure team.
* *Repository Access:*
You must have access to the source repository on Pagure and the necessary privileges to create repositories in the target organization on Fedora Forge.
* *Organization Permissions:*
You must have the ability to create repositories under the target namespace in Fedora Forge.
If you don't have these privileges, consult a member from the relevant subproject or SIG, or contact the Fedora Infrastructure team.
[IMPORTANT]
====
**Do NOT create or use an API key for standard repository migration.** The API key is only needed for migrating private tickets. Using an API key in the standard migration will cause the migrator to import only private tickets instead of the full repository content. If you haven't set the repository to private, these private tickets will become publicly visible.
**Do NOT create or use an API key for standard repository migration.**
The API key is only needed for migrating private tickets.
Using an API key in the standard migration will cause the migrator to import only private tickets instead of the full repository content.
If you haven't set the repository to private, these private tickets will become publicly visible.
====
[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.
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.
====
== Procedure
@ -53,22 +49,25 @@ include::partial$access_fedora_forge_migration_tool.adoc[]
=== Configure Repository Migration
. Fill in the migration form with the information from your source repository:
.. *Repository Name:* Enter the desired name for the migrated repository
.. *Clone URL:* Enter the Git clone URL from your Pagure repository
.. *Description:* Copy the repository description from Pagure (optional)
.. *Visibility:* Set to public for publicly accessible content
.. *Repository Name:* Enter the desired name for the migrated repository.
.. *Clone URL:* Enter the Git clone URL from your Pagure repository.
.. *Description:* Copy the repository description from Pagure (optional).
.. *Visibility:* Set to public for publicly accessible content.
.. **Leave the token field empty** - this is crucial for standard repository migration.
image:pagure_migration_form_filled.png[]
+
[WARNING]
====
**Do NOT enter an API key in the token field.** If you provide an API key here, the migrator will only import private tickets instead of the full repository content (code, public issues, pull requests, etc.). This will result in an incomplete migration. Additionally, if you haven't set the repository to private, these private tickets will become publicly visible, potentially exposing confidential information.
**Do NOT enter an API key in the token field.**
If you provide an API key here, the migrator will only import private tickets instead of the full repository content (code, public issues, pull requests, etc.).
This will result in an incomplete migration.
Additionally, if you haven't set the repository to private, these private tickets will become publicly visible, potentially exposing confidential information.
====
. Click on the *Migrate repository* button to start the migration.
image:pagure_migration_start_migration_button.png[]
image:pagure_migration_start_migration_button.png[]
. Wait for the migration to complete. This creates a repository with all publicly accessible data.
image:pagure_migration_completion_success.png[]
image:pagure_migration_completion_success.png[]
== Verification
@ -76,4 +75,4 @@ include::partial$access_fedora_forge_migration_tool.adoc[]
* Verify that all repository contents (code, branches, tags) have been successfully migrated.
* Check that issue tickets and pull requests have been transferred correctly.
* Test repository access permissions for team members.
* Verify that the repository is accessible via Git clone operations.
* Verify that the repository is accessible via Git clone operations.