{"meta":{"title":"Reviewing stacked pull requests","intro":"Address review feedback on a pull request anywhere in a stack and cascade your changes through the rest of the stack.","product":"Pull requests","breadcrumbs":[{"href":"/en/pull-requests","title":"Pull requests"},{"href":"/en/pull-requests/how-tos","title":"How-tos"},{"href":"/en/pull-requests/how-tos/review-pull-requests","title":"Review pull requests"},{"href":"/en/pull-requests/how-tos/review-pull-requests/reviewing-stacked-pull-requests","title":"Review stacked PRs"}],"documentType":"article"},"body":"# Reviewing stacked pull requests\n\nAddress review feedback on a pull request anywhere in a stack and cascade your changes through the rest of the stack.\n\n> [!NOTE] This feature is in public preview and subject to change.\n\nEach pull request in a stack shows only the diff for its layer. This means reviewers can request changes on any pull request independently. When a reviewer requests changes on a pull request mid-stack, you should make the fix on the branch that owns the change and rebase so the branches above it pick up your update.\n\n## Addressing review feedback\n\n1. Navigate to the branch that needs changes.\n\n   ```shell copy\n   gh stack checkout BRANCH-NAME\n   ```\n\n   You can also move through the stack with `gh stack bottom`, `gh stack down`, `gh stack up`, and `gh stack top`.\n\n1. Make the requested fixes, then stage and commit them.\n\n   ```shell copy\n   git add .\n   git commit -m \"helpful-commit-message\"\n   ```\n\n1. Cascade the changes through the rest of the stack. This rebases every branch above the changed one so they pick up your fix.\n\n   ```shell copy\n   gh stack rebase\n   ```\n\n1. Push the updated stack. This uses `--force-with-lease` to safely update the rebased branches.\n\n   ```shell copy\n   gh stack push\n   ```\n\nAfter you push, each pull request above the changed one reflects the update, and any CI checks are re-triggered."}