Chapter 07
Reviewing and merging pull requests
When the agent finishes a task, it doesn't merge anything on its own — it proposes a pull request and waits for you. This page covers the proposal, the approval flow, and where to review.
How a pull request is proposed
At the end of the workflow, the agent presents a PR proposal card in the chat. It shows:
- the branch and target,
- the files changed,
- the proposed commit message, and
- the proposed PR title and description.
The agent pauses here. Nothing has been committed or pushed yet.
Approving the proposal
When you approve the PR proposal, the agent carries out the sequence for you:
- Commits the staged changes with the proposed message.
- Pushes the branch to your remote repository.
- Opens the pull request on your source-control provider.
Each of these is gated by your approval — if you'd rather review the commit and push separately, you'll see the commit and push proposal cards first (see Working with the agent).
important
Where to review the pull request
You can review the proposed change in two places:
- In Vyazen — the proposal card and the agent chat give you the summary and context the agent used.
- In your source-control provider — GitHub, GitLab, or Bitbucket's standard PR view, where you can read the diff, comment, and run your usual review checks.
Most teams do the final review and merge in the provider's PR view, using Vyazen's summary to orient quickly.
Merging
Once you're satisfied, merge the pull request in your source-control provider as you normally would (merge commit, squash, or rebase per your team's convention). Vyazen doesn't merge for you — merging stays a human action.
Requesting changes or rejecting
If the work isn't right, reject the proposal (or request changes in the provider's PR view). The agent resumes the task, revises its approach, and proposes again. You can also steer it with a follow-up message in the chat describing what to fix.