Main Branch Requirement
Resolve Runner Failures Caused by Branch Naming Policies
Last updated
Was this helpful?
⌘Ctrlk
Resolve Runner Failures Caused by Branch Naming Policies
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.
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.
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.
Navigate to the Migration HQ repository on GitHub.
Go to Settings > General.
Under Default branch, change the branch name to main.
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.
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.
Failed Migration — other causes of migration failures
Failed Inventory Scan — other causes of scan failures
Troubleshooting — index of all common issues
Last updated
Was this helpful?
Was this helpful?