Ship work to a branch and pull request
Review the branch, file scope, and pull-request settings before shipping agent work.
Last updated 16 September 2026
Review the branch, file scope, and pull-request settings before shipping agent work.
Before you start
Complete the work’s review and tests. Pushing or opening a pull request requires the intended remote repository and an authenticated account with access.
Review branch, file scope, push, and PR settings before generating and executing the final shipping action.
Step by step
Open Ship from the implementation conversation. Confirm the repository and whether you are working in the main project or a Solo branch.
Choose Current or New branch. Review the branch name and select the intended changes: This chat narrows the candidate scope, while All changes can include unrelated work.
Inspect every selected file and deselect anything outside the task. Resolve any warning about staged changes outside the chosen scope.
Choose whether to Push to remote and Open pull request. When opening a PR, confirm its Base branch and review the proposed title and description.
Leave Auto off when you want a review step. Choose Generate content, then inspect the prepared branch, commit message, and PR content.
Use the final action only when its selected commit, push, and PR effects match your intent. Read the result and follow the PR link when one is created.
If a later stage fails, inspect what already succeeded before retrying. A commit may exist even if a push or PR creation failed.
What to expect
The intended changes are delivered to the chosen branch, with a pull request when selected and supported.
Troubleshooting and useful details
The screenshot shows the preflight form with three implementation files; it is not evidence that this demo code was pushed. Auto combines preparation and execution, so review its effects before enabling it. Shipping a Solo branch and Rejoining it into a local target are different workflows.