> 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/create-and-configure-your-project.md). # Create and Configure Your Project ### Objective In Warp, a ***Project*** is an object for managing the migration of repositories to GitHub. Typically, you’ll create a new project for a specific *migration engagement*, such as moving a collection of repositories for an organization, department, team, or development project. In this section, you’ll set up a Project by creating it, installing the Warp GitHub app for the organization, and configuring the Project. **At the end of this section, you will have a new Warp project.** {% 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 %} ### Sign In to the Warp Web Application 🛠️ Open a browser tab or window to the [Warp web application](https://warp.packfiles.io) at [warp.packfiles.io](https://warp.packfiles.io)

Warp's Login Page

🛠️ Click the **Sign in with GitHub** button and sign in to Warp using your GitHub account. ### Create a New Project Upon signing in, you will be taken to Warp’s *Projects* page, which lists your current migration projects:
Warp's "Projects" page, with a single project and the "Create a New Project" area.

Warp’s Projects page, which you’ll see immediately after signing in.

At the bottom of the list of projects, you’ll see the **Create a New Project** area. 🛠️ Click anywhere on **Create a New Project** area to expand it. The **Create a New Project** area will expand to display instructions for what to do next:
Close-up of the expanded "Create a New Project" area, with the steps for creating a new project and the "Install Warp from the GitHub Marketplace" button.

The Create a New Project area, after you’ve expanded it.

🛠️ Click the **Install Warp from the GitHub Marketplace** button. ### Install Warp’s Github App A new browser will open to the [GitHub Marketplace page for Warp’s GitHub app](https://github.com/marketplace/packfiles-warp):
The top of the Warp app's page in GitHub Marketplace. The "Add" button is near the upper right corner of the page.

The Warp app’s page in GitHub Marketplace.

🛠️ Click the **Add** button near the upper right corner of the page or scroll to the bottom of the page. You should see the following:
The bottom of the Warp app's page in GitHub. The "Account" and "Install it for free" buttons button is near the bottom of the page.

The Warp app’s page in GitHub Marketplace, scrolled to the bottom.

At the bottom of the page, you’ll see the **Account** drop-down menu and the **Install it for free** button:
Close-up of the "Account" drop-down menu and "Install it for free" button.
🛠️ In the **Account** menu, select the account for the destination organization — that is, the organization that you will be migrating repositories to. {% hint style="info" %} The example destination organization for this quickstart is **Hypotheticorp01**. {% endhint %} 🛠️ Click the **Install it for free** button. You’ll be taken to the **Review Your Order** page:
The "Review your order" page in GitHub Marketplace. It shows that the user is getting Warp for free, and that the version supports 1 user, 10 repositories, and migrates from Azure DevOps to GHEC.

The Review Your Order page in GitHub Marketplace.

🛠️ Review the order, then click the **Complete order** button. You’ll go to the *Install Packfiles Warp* page, which will show: * That the Warp GitHub app will have access to all the repositories in the organization, and * What read, read/write, and admin permissions it will have within the organization and its repositories.
The "Install Packfiles Warp" page on GitHub. It shows that Warp will be included for the user's organization for all repositories, with a long list of permissions.

The Install Packfiles Warp page in GitHub.

🛠️ Click the **Install** button at the bottom of the page. You will return to the Warp web app, and can proceed to the next step. ### Configure the Project You will be at the *Welcome to Warp* page:
The "Welcome to Warp" page in the Warp web app. Key items are the user's destination organization and the "Next" button.

The Welcome to Warp page.

🛠️ Click the **Next** button. This will take to you the *Configure Your Project* page:
The "Configure Your Project" page in the Warp web app. Key items are the user's project name and the "Next" button.

The Configure Your Project page.

You can do two things on this page: 1. You can set the name of your project, or choose to keep the default name. 2. You can invite people on your team to become members of the project. {% hint style="info" %} As the creator of the project, you don’t have to add yourself to the team. You are already a member of the project with *Admin* access. {% endhint %} 🛠️ For this Quickstart, simply click the **Next** button. You will arrive at the *Connect Your Sources* page. You’ll use it in the process of connecting your source and GitHub accounts to Warp:
The "Connect Your Sources" page in the Warp web app. Key items are the user's project name and the "Next" button. The key item on this page is the “Migration HQ” button.

The Connect Your Sources page.

When you created the project, Warp created a repository named *Migration HQ* for the GitHub organization that you selected earlier. *Migration HQ* will be the user interface for managing your migrations. It will be where you issue commands to Warp and it will keep track of which repositories to migrate and which ones have already been migrated. 🛠️ Let’s visit *Migration HQ*. Click the **Migration HQ** button, located in the *Set Up Your Vault* section:
The "Migration HQ" button.
A new browser tab or window will open, and you should see the *Migration HQ* page:
The "Code" page of the "Migration HQ" repository in GitHub.

The Migration HQ page for your project.

The files contained in *Migration HQ* are configuration and credentials files that Warp will use in the migration process. You will need to clone *Migration HQ* to your local computer, where you will create a *vault file* containing the following: * Credentials for accessing the repositories at the source (the place where you are migrating repositories *from*). * Credentials for accessing the destination GitHub organization (the place where you are migrating repositories *to*). After creating the vault file, Warp will automatically push it to *Migration HQ*, making the credentials available to Warp, enabling it to migrate your repositories. 🛠️ Clone the *Migration HQ* repository to your local computer. {% hint style="success" %} You’ve successfully set up your project — nicely done! Make sure that you’ve cloned *Migration HQ* to your local computer, then [proceed to the next step.](/guides/quickstart/set-up-your-vault.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/create-and-configure-your-project.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.