Migration HQ
Learn How Warp Organizes your Migration Processes
Last updated
Was this helpful?
Learn How Warp Organizes your Migration Processes
Last updated
Was this helpful?
The Migration HQ repository — the HQ is short for “headquarters” — is Warp’s primary user interface. When you create a Project, Warp generates a Migration HQ repository for that project; it’s the “control panel” that you use to manage the migration process.
You will use the page of Migration HQ most often. Warp uses this page for the list of migrations. For each repository that Warp finds in the sources you provide (e.g. Azure DevOps), it creates an issue representing that repository. Each issue acts as the user interface for managing the migration of its repository. You enter Warp commands in the issue’s Comments section, including the command to migrate the issue from the source to GitHub.
You also might these Migration HQ pages on occasion:
Actions: Warp uses GitHub Actions to perform migrations and other tasks. You can see these Action in operations and find out if they’ve completed by visiting the Actions page in Migrations HQ.
Code: Warp uses Migration HQ’s Code section to store configuration files, including:
config/vault.age: “The vault,” a file that stores the encrypted tokens that allow Warp to access the source and destination organizations.
config/warp.yml: Warp’s main configuration file, which you can customize for more complex migration actions, such as rewiring Azure DevOps pipelines to point at GitHub.
