Scan Your Sources for Repositories

Objective

With your Vault set up, Warp now has the necessary credentials to access both your source repositories and the destination GitHub organization.

Warp now needs to scan your source to compile a list of repositories for migration. You’ll do this with the Warp web application and look at the results in Migration HQ.

At the end of this section, you will have a list of repositories for migration.

Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow.

Verify Your Credentials

🛠️ Go back to the Warp browser tab or window. It should be on the Connect Your Sources page, which should look like this:

Warp’s Connect Your Sources page.

The next step is to connect your Azure DevOps account to Warp. This will allow Warp to access the repositories you want to migrate from Azure DevOps to GitHub.

🛠️ Go back to the Warp browser tab or window. Make sure that you’re on the Connect Your Sources page shown above, then click the Check Credentials button near the lower right corner of the page.

The text in the Verify Credentials section will change to “We’re checking your Vault’s credentials. This will take a moment...”:

Warp’s Connect Your Sources page, with Warp checking the credentials stored in the Vault.

🛠️ While Warp is examining your vault, switch to the browser tab or window that you were using for the Migration HQ repository in GitHub and select the Actions tab.

This will display the list of Migration HQ’s workflows:

Migration HQ’s Actions page with an active Warp Runner Agent.

If you switch to the GitHub browser tab or window and clicked the Actions tab quickly enough, you should see a workflow with a spinning yellow icon named Warp Runner Agent. The yellow icon denotes that it is currently running. This workflow is using the vault key you stored in Migration HQ’s secrets to unlock the personal access tokens for Azure DevOps and GitHub.

🛠️ Wait until the spinning yellow icon is replaced by a green checkmark. This means that the vault key was successfully used to unlock the personal access tokens for Azure DevOps and GitHub.

Migration HQ’s Actions page with a Warp Runner Agent that has completed its task.

🛠️ Switch back to the browser tab or window for Warp:

Warp’s updated Connect Your Sources page.

You should see a section below Verify Credentials titled Your Vault. It should contain two items:

• An item representing the Azure DevOps Organization containing the repositories you want to migrate, and

• An item representing the GitHub organization where you want to migrate the repositories.

If you don’t see these items, click your browser’s Refresh button.

🛠️ Click the Next button.

You’ll arrive at the All Done! page, which marks the end of the process of configuring the project:

The Review and Complete page.

Check the Project’s Status

🛠️ Let’s check the project’s status. Click the Go to Dashboard button.

Check the Project’s Status

The Dashboard page shows the status of the project you just configured:

The Dashboard page.

The Trends section displays the following statistics:

• The number of repositories that Warp found in the Azure DevOps Organization,

• the number of repositories that have been migrated to GitHub,

• the average number of repositories that have been migrated per day, and

• the overall progress of the migration, expressed as a percentage.

The text above the Trends section says “Tasks in Progress” and “Scanning your sources...” Warp is scanning your Azure DevOps organization for repositories. Let’s see this process in action.

🛠️ Switch to the browser tab or window for the Migrations HQ repository and select the Actions tab:

The Actions page of Migration HQ, showing the Runner Agent scanning the Azure DevOps organization for repositories.

You should see a new workflow with a spinning yellow icon named Warp Runner Agent. The yellow icon denotes that it is currently running. This workflow is scanning the Azure DevOps organization for repositories.

🛠️ Wait for the Warp Runner Agent workflow to start and finish. You’ll know it’s finished when the spinning yellow icon is replaced by a green checkmark. The process may take a few minutes, depending on how many repositories are in your Azure DevOps organization:

The Actions page of Migration HQ, showing the Runner Agent having completed its task.

🛠️ When the Warp Runner Agent has finished its tasks, switch back to the browser tab or window with the Warp Dashboard:

Warp’s Dashboard page, after scanning for sources.

You should see the updated statistics on the Dashboard page. The number of repositories found in the Azure DevOps Organization should now be displayed.

If you don’t see a count of discovered Azure DevOps repositories, click your browser’s Refresh button.

Of course, the best way to prove that Warp has successfully scanned the source and found repositories is to go to Migration HQ and look at the Issues section.

🛠️ Switch to the browser tab or window with Migration HQ and click the Issues tab.

You’ll be taken to Migration HQ’s open issues list:

Migration HQ’s Issues page.

You’ll see that the number of issues in the list is that same as the number in the Repositories Discovered entry in the Dashboard.

If you take a closer look at the open issues list...

The open issues list, close up.

...you’ll see that each issue corresponds to a repository from your source.

You’re so close now — it’s time to start migrating!