Review and merge a pull request

Check an agent's changes, tests and preview, then approve and merge the pull request or send it back with changes.

On this page

When an agent finishes building and its checks pass, the run asks for a review: Review pull request. You can review in Duun, on GitHub or both. Whatever you decide is reflected in both places.

Review the changes

  1. Open the Review pull request ask from your Inbox or from Reviews in the sidebar.
  2. Open the Changes tab to read the diff. Files are listed on the left with lines added and removed. Select a file to read it.
  3. Open the Checks tab to see test and CI results. The tab shows how many checks passed, for example 18/18. Select a check to read its log.
  4. Open the Preview tab if the run produced one. UI changes usually come with a live preview and screenshots you can click through.
  5. Read the run’s conversation for anything the agent flagged. Agents note what they didn’t verify and what they left out of scope.

Approve and merge

If everything looks right, select Approve & merge, or press ⌘ ↵. Duun approves the pull request and merges it according to the factory’s merge mode. The run then finishes and moves to Settled today in your Inbox.

Request changes

  1. Select Request changes.
  2. Describe what needs fixing, as you would in a code review. Point at files or behaviour: “Handle the case where provider_event_id is null.”
  3. Send it. The agent makes the changes on the same branch, re-runs the checks and asks for review again.

Comments you leave on the pull request in GitHub reach the agent too.

How merging works

Each factory’s Deliver step has one of three modes:

ModeWhat happens
Merge on greenDuun squashes and merges once checks and reviews pass
Open PR onlyA person merges the pull request
Draft PRThe PR stays a draft, for early feedback

With Merge on green, your approval is the last thing needed. With Open PR only, approving in Duun approves the PR and you or a teammate merge it in GitHub.

If something goes wrong

  • A check failed. Select Re-run checks on the Checks tab if it looks flaky, or see Checks are failing.
  • Merge is blocked. Your repository’s branch protection may need another reviewer or a CODEOWNER. Duun follows those rules.
  • You merged by mistake. Revert the pull request in GitHub as you normally would. You can start a new run to fix forward.

Developers can configure merge modes and review gates in Step kinds.

    Type to search the docs, help center and blog.