> 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/using-warp/support/troubleshooting/main-branch-requirement.md).

# Main Branch Requirement

Warp requires the Migration HQ repository's default branch to be named `main`. If your GitHub organization enforces a different default branch name (e.g., `master`, `develop`, `trunk`), the Warp Runner Agent will fail to execute.

## Symptoms

* Runner Agent fails immediately after any Warp operation.
* No workflow runs appear in Migration HQ's Actions tab, or they fail during setup.
* Warp does not respond to slash commands.

## Cause

Warp's runner workflows are configured to execute on the `main` branch. GitHub organizations can set an organization-level default branch naming policy that overrides the default for all new repositories. When this policy is set to something other than `main`, the Migration HQ repository is created with a different default branch name, and Warp's workflows cannot run.

## Resolution

1. Navigate to the Migration HQ repository on GitHub.
2. Go to **Settings** > **General**.
3. Under **Default branch**, change the branch name to `main`.

{% hint style="info" %}
If your organization enforces a branch naming policy, you can temporarily change the organization-level default to `main` before installing Warp. Once the Migration HQ repository is created with `main` as its default branch, you can change the organization-level policy back. The Migration HQ repository will retain `main` as its default branch.
{% endhint %}

## Prevention

Before installing Warp, verify that either:

* Your organization's default branch naming policy is set to `main`, or
* You are prepared to manually change the Migration HQ repository's default branch to `main` after it is created.

## Related Pages

* [Failed Migration](/using-warp/support/troubleshooting/failed-migration.md) — other causes of migration failures
* [Failed Inventory Scan](/using-warp/support/troubleshooting/failed-inventory-scan.md) — other causes of scan failures
* [Troubleshooting](/using-warp/support/troubleshooting.md) — index of all common issues


---

# 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, and the optional `goal` query parameter:

```
GET https://kb.packfiles.io/using-warp/support/troubleshooting/main-branch-requirement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.