vault.age file at runtime (and only with the your vault master key stowed in GitHub’s repository secrets).
The last component is the Migration HQ repository that Warp automatically generates during the Warp installation and configuration process of your migration project. It’s here in the Migration HQ repository that you can update the runtime configuration settings for Warp Runner Agents (see the warp.yml file). Warp will create a GitHub Issue for each git repository in your source (e.g., ADO Organization). From there you can plan, coordinate, and collaborate on your migration to GitHub.
The following diagram shows how these components fit together:
- Advanced security features that are seamless, easy to use, mitigate risk, and respect your privacy,
- A fair, flexible, and transparent licensing model with no surprises,
- Built in reporting and project management tools that make work visible, collaborative, and straightforward to plan,
- A GitHub-native experience that lets your team use the tools they already know and love, and
- A wide range of available support options to assure the success of your team, directly from our team and from our expert partners.