> For the complete documentation index, see [llms.txt](https://kb.packfiles.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.packfiles.io/guides/quickstart/scan-your-sources-for-repositories.md).

# 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.**

{% hint style="info" %}
Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow.
{% endhint %}

### 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:

<figure><img src="/files/5Q1L8Mbt3nysHyHz4raU" alt="Warp’s “Connect Your Sources” page. The key item is the “Check Credentials” button near the lower right corner of the page."><figcaption><p>Warp’s <em>Connect Your Sources</em> page.</p></figcaption></figure>

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...”:

<figure><img src="/files/CWNbvtuRF7Sk6sMsUK5C" alt="Warp’s “Connect Your Sources” page. The “Verify Credentials” section has been updated to read “We’re checking your Vault’s credentials. This will take a minute or two…”"><figcaption><p>Warp’s <em>Connect Your Sources</em> page, with Warp checking the credentials stored in the Vault.</p></figcaption></figure>

🛠️ 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:

<figure><img src="/files/U7zXzRL2GiKFq2bXkHBf" alt="Migration HQ’s Actions page with an active Warp Runner Agent."><figcaption><p><em>Migration HQ</em>’s <em>Actions</em> page with an active Warp Runner Agent.</p></figcaption></figure>

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.

<figure><img src="/files/F8ZkBiqXdGSxlkzwF7FO" alt="Migration HQ’s Actions page with a Warp Runner Agent that has completed its task."><figcaption><p><em>Migration HQ</em>’s <em>Actions</em> page with a Warp Runner Agent that has completed its task.</p></figcaption></figure>

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

<figure><img src="/files/uLp0qYZDOGViuniGvKjI" alt="Warp’s updated Connect Your Sources page. The &#x22;Verify Credentials&#x22; section now contains a new subsection called &#x22;Your Vault&#x22; which contains entries for Azure DevOps and GitHub."><figcaption><p>Warp’s updated <em>Connect Your Sources</em> page.</p></figcaption></figure>

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:

<figure><img src="/files/1tyarUmQi3qIAUzwRfyL" alt="The Review and Complete page. The text reads &#x22;You’re all set! Check out your Project dashboard to view metrics, manage settings, get support, and more. When you’re ready to start migrating, visit Issues in your Migration HQ repository.&#x22;"><figcaption><p>The <em>Review and Complete</em> page.</p></figcaption></figure>

### 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:

<figure><img src="/files/veQc9KLhuGv25HR3Yeoz" alt="The “Dashboard” page. At the top of the page is a notice that says “Tasks in Progress — Scanning your sources…” The “Trends” section shows repository statistics: Repositories Discovered (0), Repositories Migrated (0), Daily Average (“N/A”), and Overall Progress (“N/A%”)."><figcaption><p>The <em>Dashboard</em> page.</p></figcaption></figure>

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:

<figure><img src="/files/Rj5ncaijsFBYQG4LTROu" alt="Migration HQ’s &#x22;Actions&#x22; page with a new active Warp Runner Agent."><figcaption><p>The <em>Actions</em> page of <em>Migration HQ</em>, showing the Runner Agent scanning the Azure DevOps organization for repositories.</p></figcaption></figure>

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:

<figure><img src="/files/6oGVosysg7szwGzcgmYu" alt="Migration HQ’s &#x22;Actions&#x22; page with the Warp Runner Agent having completed its task."><figcaption><p>The <em>Actions</em> page of <em>Migration HQ</em>, showing the Runner Agent having completed its task.</p></figcaption></figure>

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

<figure><img src="/files/Brl0d7STg6MJlGHhDDi9" alt="The updated “Dashboard” page. The “Trends” section shows repository statistics: Repositories Discovered (5), Repositories Migrated (0), Daily Average (“N/A”), and Overall Progress (“0.0%”). There is a new section below “Trends” called “By source”, and it has one source: joey-ado-testing (5)."><figcaption><p>Warp’s <em>Dashboard</em> page, after scanning for sources.</p></figcaption></figure>

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:

<figure><img src="/files/pbbt4XwmTpZo7DJtSiCs" alt="Migration HQ’s &#x22;Issues&#x22; page, which contains 5 issues."><figcaption><p><em>Migration HQ</em>’s <em>Issues</em> page.</p></figcaption></figure>

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...

<figure><img src="/files/sq8FigQKB4D3EX94EZOU" alt="Migration HQ’s &#x22;Issues&#x22; page, with the open issues list close up."><figcaption><p>The open issues list, close up.</p></figcaption></figure>

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

{% hint style="success" %}
You’re so close now — it’s time to [start migrating!](/guides/quickstart/migrate-a-repository.md)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.packfiles.io/guides/quickstart/scan-your-sources-for-repositories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.