> 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/migrate-a-repository.md). # Migrate a Repository ### Objective At last, it’s time to migrate a repository to GitHub! You’ll do this entirely in *Migration HQ*. **At the end of this section, you will have a repository that has been migrated from its source and into your GitHub organization.** {% 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 %} ### Select a Repository to Migrate After scanning your source for repositories, you navigated to *Migration HQ*’s *Issues* page, where you saw the open issues list:

Migration HQ’s Issues page, with a close-up view of the open issues list. — *Migration HQ*’s *Issues* page, with a close-up view of the open issues list.

Each item in the open issues list represents a repository to be migrated. After migrating a repository, Warp automatically closes its issue, which moves it to the closed issues list. Let’s migrate a repository! For this example, we’ll migrate **TailwindTraders-Website**, whose issue is at the top of the open issues list pictured above. 🛠️ In your open issues list, click on the issue for the repository you want to migrate. The page for the issue will appear:

The page for the TailwindTraders-Website issue. — The page for the *TailwindTraders-Website* issue.

### Migrate the Repository 🛠️ Scroll to the comments section at the bottom of the issue page:

The "Add a comment" box at the bottom of the page for the "TailwindTraders-Website" issue. — The *Add a comment* box at the bottom of the page for the *TailwindTraders-Website* issue.

You issue commands to Warp in comments by using *slash commands* — commands that begin with the slash (`/`) character. One of these commands is /migrate, which tells Warp to migrate the repository represented by this issue. 🛠️ Enter the slash command `/migrate` into the comment box and click the **Comment** button. A couple of seconds later, Warp will confirm that it received the command. The comments section will look like this:

The comments section of the page for the TailwindTraders-Website issue. The first comment, by the user “AccordionGuy”, says “/migrate”. The follow-up comment, by the user “packfiles-warp”, says “@AccordionGuy, your migration’s in progress! We’ll let you know when it’s complete.” — The comments section of the page for the *TailwindTraders-Website* issue.

Warp — which will have the user name **packfiles-warp** — always provides a response to your commands as a follow-up comment. In the example above, it’s notifying you that the migration process has begun. It typically takes a few minutes to perform a migration. Let’s use this time to watch the migration’s progress. 🛠️ Switch to *Migration HQ*’s *Actions* page by clicking the **Actions** tab:

Migration HQ’s Actions page with a new active Warp Runner Agent. — *Migration HQ*’s *Actions* page.

You’ll see a new Warp Runner Agent running the workflow that performs the migration:

🛠️ Click on the Runner Agent to get a closer look at what it’s doing. You’ll see the Runner Agent’s page:

Let’s get an even closer look at what the Runner Agent is doing. 🛠️ Click on the job that the Runner Agent is running — it’s any of the objects onscreen labeled **Packfiles Warp Runner Agent** that has a spinning yellow icon beside it:

You’ll go to a page where you can see the log files that the job is generating in real time:

The logs for the Warp Runner Agent. — The logs for the Warp Runner Agent, while the Agent is running.

A couple of minutes later, the migration will be complete. You’ll know this has happened when the Runner Agent’s icon changes from spinning and yellow to a static green checkmark:

The logs for the Warp Runner Agent, after the Agent has completed its task.

🛠️ Click the **Actions** tab to return to the top level of the *Actions* page. You’ll see that the Runner Agent completed its tasks:

Migration HQ’s Actions page after the Warp Runner Agent has completed its task. — *Migration HQ*’s *Actions* page.

### Examine Your Migrated Repository With the Runner Agent’s tasks complete, your repository has been migrated! Let’s look at its issue. 🛠️ Click the **Issues** tab to view the *Issues* page. You’ll see something like this:

Migration HQ’s "Issues" page, with the open issues list displayed. The open issues list displays 4 items. — *Migration HQ*’s *Issues* page — the open issues.

Notice that: * There’s one less item in the open issues list, and * There one new item in the formerly empty closed issues list. 🛠️ Click the **Closed** tab to view the closed issues list. You’ll see the issue for the newly migrated repository:

Migration HQ’s "Issues" page, with the closed issues list displayed. The closed issues list displays 1 item. — *Migration HQ*’s *Issues* page — the closed issues.

🛠️ Click the issue to view its details:

You’ll see that the issue has been updated:

The updated page for the "TailwindTraders-Website" issue. Its content now indicates that the repository has been migrated. — The updated page for the *TailwindTraders-Website* issue.

🛠️ Scroll to the comments section at the bottom of the page. You’ll see a new comment from Warp, followed by a new notification:

The newest comment on the "TailwindTraders-Website" issue page. The comment says "@AccordionGuy, your migration was successful. Visit your new code’s home at TailwindTraders.TailwindTraders-Website." — The newest comment on the *TailwindTraders-Website* issue page.

The comment informs you that the migration was successful and provides a link to the newly migrated repository. The notification below the comment informs you that Warp automatically closed this issue. 🛠️ Confirm that the migration was successful by clicking the link in the comment. In this example, the link is the text **Tailwind-Traders.TailwindTraders-Website**. Here’s what the example migrated repository looks like:

The "Code" page for the migrated Tailwind-Traders repository. — The migrated Tailwind-Traders repository.

{% hint style="success" %} 🙌 Congratulations — you did it! 🙌 You successfully migrated a repository! {% 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/migrate-a-repository.md?ask= ``` 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.