Migrate a Repository

Objective

Transfer the explicitly selected repository state to a verified destination with auditable completeness, no credential leakage, and a controlled cutover/recovery plan.

Use When

• Mirror all intended branches/tags/notes or a declared ref subset to a new host.
• Migrate Git LFS objects and validate submodule/repository dependencies.
• Change hosting with default branch, permissions, branch/tag policy, and collaborator cutover.
• Perform a repository-wide filter only when required by the migration postcondition.

Do Not Use / Route Elsewhere

• Use manage-remotes to add/change one remote.
• Use sync-branches to push one ordinary branch.
• Use setup-repository for a development clone.
• Use provider-specific tooling for issues/PRs/wiki/releases unless explicitly included and supported.