<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=585576) </details> <!--IssueSummary end--> In order to maintain feature parity with direct transfer, offline transfer will need to export project and group wikis to files as well. ## Proposed implementation Wikis on groups and projects are their own git repositories, so we should be able to export them similarly to project repositories: - Add `'project_wiki'` relation to [BulkImports::FileTransfer::ProjectConfig](app/models/bulk_imports/file_transfer/project_config.rb) and `'group_wiki'` relation to [BulkImports::FileTransfer::GroupConfig](app/models/bulk_imports/file_transfer/group_config.rb) as file reltions. - In [`BulkImports::FileExportService`](app/services/bulk_imports/file_export_service.rb), add a case for project and group wikis and call `RepositoryBundleExportService` with `portable.wiki.repository` - Exporting to object storage should be handled in https://gitlab.com/gitlab-org/gitlab/-/work_items/585537 - Skip these relations if not part of an offline transfer export - Only export group wikis in EE In direct transfer, the destination wiki fetches the source wiki as a mirror. Mirroring won't be possible, so that will simply be a limitation of offline transfer.