Add support for migrating from Pagure (#8513)

Add support for migrating Pagure repositories (including metadata) to Forgejo via the migration tool.

One 'discrepancy' with migration from other forges is how privates issues are handled, they are migrated when a API token is set for the migration, in that case users are advised to set their repositories visibility to private to avoid leaking such private issues.

Co-authored-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
Co-authored-by: Ryan Lerch <rlerch@redhat.com>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/8513
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-committed-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
This commit is contained in:
Akashdeep Dhar 2025-08-11 16:56:26 +02:00 committed by Gusted
commit b8f15e4ea0
59 changed files with 6921 additions and 1 deletions

View file

@ -117,5 +117,12 @@
"og.repo.summary_card.alt_description": "Summary card of repository %[1]s, described as: %[2]s",
"repo.commit.load_tags_failed": "Load tags failed because of internal error",
"compare.branches.title": "Compare branches",
"migrate.pagure.description": "Migrate data from pagure.io or other Pagure instances.",
"migrate.pagure.incorrect_url": "Incorrect source repository URL has been provided",
"migrate.pagure.project_url": "Pagure project URL",
"migrate.pagure.project_example": "The Pagure project url, e.g. https://pagure.io/pagure",
"migrate.pagure.token_label": "Token",
"migrate.pagure.token_body_a": "Provide a Pagure API token with access to the private issues to create a repository with just the private issues in it",
"migrate.pagure.token_body_b": "Be sure to set the private repo flag above if you want this repo to be private",
"meta.last_line": "Thank you for translating Forgejo! This line isn't seen by the users but it serves other purposes in the translation management. You can place a fun fact in the translation instead of translating it."
}