> 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-restack-1.md). # av-restack Command Guide Optimize stacked pull requests using the av-restack command in Aviator CLI. ### NAME av-restack - Rebase the stacked branches ### SYNOPSIS ```synopsis av restack [--dry-run] [--continue | --abort | --skip] ``` ### DESCRIPTION `av restack` is a command to re-align the stacked branches. When a parent branch is amended or has a new commit, the children branches need to be rebased on the new parent. This command does the rebase operation for all the branches in the current stack. This command does not push the changes to the remote. ### REBASE CONFLICT Rebasing can cause a conflict. When a conflict happens, it prompts you to resolve the conflict, and continue with `av restack --continue`. This is similar to `git rebase --continue`, but it continues with syncing the rest of the branches. ### OPTIONS `--all` : Rebase all branches. `--current` : Only rebase up to the current branch. (Don't recurse into descendant branches.) `--continue` : Continue an in-progress rebase. `--abort` : Abort an in-progress rebase. `--skip` : Skip the current commit and continue an in-progress rebase. `--dry-run` : Show the list of branches that will be rebased without actually rebasing them. ### SEE ALSO `av-sync`(1) for syncing with the remote repository. --- # 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/manpages/av-restack-1.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.