Git and pull requests
Give every task its own branch, review the diff, and open a pull request without leaving ADE.
On this page
A branch for every task#
Each new task in a git repository gets its own branch, a separate line of changes. It also gets its own worktree, a second checkout of the same repo, so the task has its own copy of the files. Tasks run in parallel without touching each other or your main checkout.
- A new task branches off the repository default branch.
- Use New task from branch to start from a remote branch or an open pull request instead. A pull request asks GitHub to merge one branch into another.
- The base you pick becomes the task target. That is the base for the diff and for the pull request.
- Re-point the target from the menu next to the branch name in the chat header.
- A folder you opened in place gets no worktree. The agent edits it directly.
Retargeting is guarded
The target cannot change while the agent runs or while a pull request is open. If the worktree is clean and untouched, ADE moves the task straight onto the new base.
Review before you ship#
The right panel tracks the task diff against its target. Comment on it yourself, ask for an AI review, or get a second opinion from Codex. Reviews run in their own chat, so they stay out of the chat that produced the changes.
| Review | How it works |
|---|---|
| Your comments | Click the + in the diff gutter next to a line or a range, write in Add a comment for the AI, and choose Comment. |
| AI review | Choose Review in the header. It opens a fresh review chat on the diff with your Review model, and its findings appear inline on the diff. |
| /codex-review | Gets an independent Codex read of the same changes when both agents are connected. |
| /codex-challenge | Asks Codex to argue against the approach and its tradeoffs. |
| /security-review | Checks the pending changes on the branch. |
Your comments go with your next message
There is no separate send button. Pending comments attach to your next normal message in that chat, but not to a slash command or a queued message.
Checks and pull request status#
- The Checks section of the git status panel shows CI results for the branch.
- When checks fail, choose Fix errors to send the failures to the agent.
- Status rows show where the pull request stands, such as Waiting for PR review, PR changes requested, or Automated review running.
- On PR changes requested, Add comments to prompt hands the reviewer comments to the agent.
Open and land a pull request#
Pull request actions live in the right panel header. They run through the GitHub CLI, so they follow the permissions of your gh login.
| Action | What it does |
|---|---|
| Commit & Push | Stages everything, commits with your message, and pushes. |
| Push / Pull | Pushes to or pulls from the branch’s remote. |
| Create PR | Opens a pull request against the task target. |
| Create draft PR | Opens the pull request as a draft. Mark it ready later from the same menu. |
| Create PR manually | Opens the GitHub pull request page in your browser instead. |
| View PR | Replaces Create PR once a pull request is open. |
| Merge | Squash-merges the open pull request. |
| Auto-merge | Turns GitHub auto-merge on or off. |
| Resolve conflicts | Asks the agent to resolve merge conflicts on the branch. |
After the merge
After a merge, the right panel offers Continue or Archive. Continue starts a fresh branch in the same task and keeps its chats. Archive closes the task out.
Act on review comments#
The Git panel lists unresolved review threads while a pull request is open. It hides resolved and outdated threads, so what you see is what still needs an answer.
- Open a thread to jump to that comment on GitHub.
- Add the threads to the chat. The agent gets the reviewer’s comments as context and works through them.
- The panel refreshes when the agent finishes, so new pushes and resolved threads appear without a manual reload.
What you need#
- A git repository with a remote for branch and pull request actions.
- The GitHub CLI signed in. ADE prompts you once if it is not.
- Code mode. VideoDraft mode hides the git controls, though worktrees still back each task.
ADE hides or disables the actions that change the repo while any chat in that task is running. Status and browser links stay available. The busy state covers one task only, so a commit in one task never blocks the git controls in another.