> 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/how-to-guides/creating-stacked-prs.md). # How to Create Stacked PRs in CLI Documentation on creating Stacked PRs with av CLI from Aviator. ### Creating a Branch Run the command ``` av branch ``` to create a new branch. If you're currently on the trunk branch of your repository (usually `main` or `master`), this will create a new stack. Otherwise, the command will create a branch that is stacked on top of your checked-out Git branch before running the command. You can stack a branch even if the first (root) branch wasn't created with the `av branch` command. ### Creating a Branch and Committing Alternatively, you can take advantage of ``` av commit -b -m "" ``` This will create a new branch, with an automatically generated branch name based on the commit message, and then commit the changes to the new branch with the given message. ### Creating a Pull Request Create the stacked PR using the following command: ``` av pr ``` By default, this will create the PR title and body based on the headline and message of the first commit in the branch (see `av pr --help` for details on how to override this). To create PRs for each branch in the stack you can do `av pr --all` . Alternatively, you can run `av pr --all --current` to only create PRs up to branch you currently have checked out in the stack. You can also [adopt a PR created without using the CLI](/aviator-cli/how-to-guides/adopt-a-branch.md#adopting-an-existing-pr). --- # 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/how-to-guides/creating-stacked-prs.md?ask=&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.