> 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/manpages/av-git-interaction-7.md).

# av-git-interaction Command Guide

### NAME

av-git-interaction - av CLI Git Interaction

### BRANCH CREATION AND ADOPTION

Typically in Git, a branch is created with `git branch`, `git switch`, or `git checkout`. Since `av` needs to keep track of the extra information about branches such as the parent branch, we have `av-branch`(1) to create a new branch and track the necessary information. This metadata is stored in `.git/av/av.db`. We call the branches that `av` has metadata for as "managed branches", and the branches that av doesn't have metadata for as "unmanaged branches".

There is a case where you created a branch without going through `av-branch`(1). In this case, you can attach the branch metadata by using `av-adopt`(1). The opposite can be done with `av-orphan`(1).

### BRANCH DELETION

When you merge a branch, `av-sync`(1) will prompt you to delete the merged branches. However, there can be a case where you want to delete a branch that is not merged yet. In this case, you can delete the branch with `git branch -d|-D`.

When you delete a branch with `git branch -d|-D`, the branch metadata is still kept in `.git/av/av.db`. Next time you run `av` command, it'll be automatically removed.

If a deleted branch has a child branch, the child branch will be orphaned. This means that the child branch still exists in the Git repository, but `av` will not manage it. In order to add it back to `av`, you can use `av-adopt`(1).


---

# 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://docs.aviator.co/aviator-cli/manpages/av-git-interaction-7.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.