Forgejo ↔ GitHub: Can we migrate a repo without downtime?

Migrating a Small Application from GitHub to Forgejo

The goal is to move the repository while keeping the application online, preserving webhooks, CI pipelines, and branch protection rules.

Constraints include the lack of an automated bulk webhook export, the need to manually recreate branch protection settings, and the temporary database lock required for a full export‑import. Forgejo’s mirror feature supports read‑only sync, but it does not propagate CI job definitions or required status checks.

Unresolved decisions revolve around whether to accept a brief webhook outage, implement a custom migration script, or rely on parallel CI pipelines and traffic switching.

What is the recommended strategy to maintain webhook continuity during the migration? Can Forgejo’s mirror be used to keep CI pipelines running while traffic is redirected? Is there an official method to migrate branch protection rules without manual recreation?