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

Pagure migration doc: add follow-up checklist based on ours

Browse source 
As we (Quality team) were doing our migrations to Forge, we came
up with a checklist and some supplemental migration tools. This
adds a slightly tweaked version of the checklist to the migration
doc as we think it will be helpful for all other teams.

See quality/tickets#836
for the original.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2026-02-10 12:01:40 -08:00
commit e8676cdfa7
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -76,3 +76,25 @@ image:pagure_migration_completion_success.png[]
* 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.
== Next steps
Based on early migrations, we offer this list of recommended next steps after repository migration.
. Copy over the project URL for Forge manually. From _Pagure project -> Settings -> Project Details -> Project's url_ into _Forge project -> Settings -> Repository -> Website_.
. xref:../migrating_issue_dependencies.adoc[Migrate assignees and dependencies]. Verify that it worked correctly. Also inspect script output.
. Use link:https://forge.fedoraproject.org/quality/forge-helpers[pagure_add_migration_comment.py] to add a migration comment to all tickets in Pagure. Verify that they it worked correctly. Also inspect script output.
. Use link:https://forge.fedoraproject.org/quality/forge-helpers[forge_convert_labels.py] to convert priority labels to the Forge standard ones: the migration tool creates separate priority labels for each repository. Check your organization has the Forge standard labels first, with the IDs listed in the script. If your project's priorities don't match those the script can handle, please send a pull request.
. In _Pagure project -> Settings -> Project Options_, enable _Issue tracker read only_ and disable _Pull requests_.
. Replace the README contents of the Pagure repo with a message:
+
```
** This project has been moved to: $NEWURL **
This repository is now in archive mode only. There will be no further responses to any issues or pull requests in this repository. The development will only be taken forward in the new repository.
```
. In _Forge project -> Settings -> Units_, disable the _Wiki_ unless you really want it. You may also want to adjust the _Merge styles_ and _Default merge style_ to your preference.
. If you use any kanban boards in the source repo, you need to re-create them manually in the new Forge repo. In Forge they are called _projects_ and can be created at the organization and/or repository level.
. Go through all source code, internal and external documentation, RPM spec files, and any other locations, find references to the old repo and replace it with the new URL. This might take a while, perhaps file a ticket for this so that you don't forget about it to do it later.
. If your repo uses CI, migrate it. You cannot use Zuul CI with Forge as you could with pagure.io. The easiest alternative is Forgejo Actions, which works much like GitHub Actions. You can get inspiration from link:https://www.happyassassin.net/posts/2026/01/19/ci-and-llm-review-on-fedora-forge-with-forgejo-actions/[Adam's howto blogpost], the link:https://forge.fedoraproject.org/quality/fedfind/src/branch/main/.forgejo/workflows[fedfind repo] and link:https://forgejo.org/docs/next/user/actions/quick-start/[Forgejo Actions documentation].
. The link:https://forge.fedoraproject.org/quality/forge-helpers[forge-helpers] repository contains scripts for converting the custom _story_points_ field to a label and converting migrated priority labels to Forge-standard ones, but it's likely you can't use either directly. The story point script is only applicable if you had the custom _story_points_ field in your Pagure repo. The label conversion script will only work as intended if you have the Scrum labels in your Forge organization and they have the same IDs the script expects - check this before running it.