Skip to main content
When the base branch has moved ahead of a pull request, Assert prepares a merge candidate: the PR merged with the latest base branch. You can review the result and use it to update the PR. If the merge has conflicts, an agent resolves them in an isolated sandbox, and you can inspect the resolution.

​
Reviewing a candidate

When Clean candidate ready appears in the review header, open it to see what the merge adds to the PR. Check the resolution and how it interacts with the PR’s changes. The Clean candidate ready pill in the review header

​
Updating the branch

To apply the candidate, choose Update branch with merge commit. This adds the merge commit to the PR branch without rewriting its history. If you have the branch checked out locally, run git pull to get it. Use Re-review to check later changes. Updating the branch doesn’t approve or merge the PR.
The Merge commit dropdown beside the candidate controls how the PR eventually lands on its base branch: merge, squash, or rebase.

​
Automatic updates

In Account settings → Merge Conflict Resolution, choose whether Assert updates pull requests you authored in that workspace: These settings only update the PR branch; they don’t approve or merge it.