As part of the ongoing RelEng migration effort, we need to migrate the pungi-fedora repository from Pagure to Forgejo. This repository is central to Fedora’s compose process and is referenced by several automation pathways within RelEng and Infra.

This work must be completed in Sprint 5, with the first week dedicated to investigation and the second to implementation. The deadline for completion is two weeks from now.

Phase 1: Investigation (Week 1)

Tasks:
- Identify all existing branches, active PRs, tags, and metadata in Pagure.
- Audit CI configs, webhooks, compose triggers, and any automation that directly references pungi-fedora.
- Document dependencies linking pungi-fedora to Pungi, compose automation, and other RelEng workflows.
- Check for open issues and review if any need handling before migration.

Phase 2: Implementation (Week 2)
Tasks:
- Run repository migration to Forgejo using the official migration tool.
- Verify:
Commit history
All branches and tags
Issues, labels, milestones
Existing Pungi/compose hooks
- Update all references from Pagure → Forgejo in RelEng tooling.
- Disable issue tracker in Pagure and replace repository with a README redirect.

Acceptance Criteria:
- Repository migrated to Forgejo successfully with all metadata preserved.
- Compose-related integrations continue functioning without disruption.
- Pagure repository fully cleaned up and redirected.
- Documentation updated with new repo location.