> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/aviator-cli/faqs-and-troubleshooting/updating-default-branch-from-master-to-main.md).

# Default Branch Update Master to Main

Documentation on updating default branch from master to main when using StackedPRs CLI.

If you choose to switch over the default branch, for instance from master to main, a few steps must be taken to update Stacked PRs CLI to handle this change:

### 1. Ensure that local remote HEAD is updated

You can do this with `git remote set-head origin --auto`.

You can read the git man page for more details:\
<https://git-scm.com/docs/git-remote#Documentation/git-remote.txt-emset-headem>

### 2. Modify .git/av/av.db file to replace the parent

In your repository `.git` directory has a file named `.git/av/av.db`. This file is a JSON document. If you open that, you can see sections like this:<br>

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2F1dLcvEn9CgBaHQSVwXz4%2Fimage.png?alt=media&amp;token=faad4e7d-b613-4d76-aab5-90aaec6e41a9" alt=""><figcaption></figcaption></figure>

This file is used by the `av` CLI to track each branch's parent. You can change `master` to `main` or whatever default branch name change you are making for all existing branches. If you are unsure, please take a backup.

\
With these two steps, av should recognize main as master, including existing branches.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aviator.co/aviator-cli/faqs-and-troubleshooting/updating-default-branch-from-master-to-main.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.