Pull requests
The three ways Sazabi works with your pull requests — opening one with a proposed fix, reviewing new ones, and answering questions from a comment.
Once you connect a forge — GitHub or Bitbucket — Sazabi works with your pull requests in three distinct ways. They are independent: you can use any one without the others.
- Opens a pull request with a proposed fix during an investigation.
- Reviews new pull requests with inline comments and a verdict.
- Answers questions you ask by mentioning it in a pull request comment.
Requirements
All three paths need a connected forge with the relevant repositories mapped to your project:
Agent-opened pull requests
When the agent identifies a concrete code change that would address what it found during an investigation, it can open a pull request with that proposed fix on your connected forge. The pull request lands in your repository like any other — with a branch, a diff, and a description of the change and why — so you review and merge it through your normal process. Nothing merges automatically; the agent proposes, you decide.
An agent-opened pull request is an ordinary pull request once it exists, so it can itself be reviewed — including by Sazabi's own automated code review if you have that enabled.
Automated review
Sazabi can review new pull requests on your connected forge, posting inline comments and an overall verdict. Review is gated by a per-project master switch under Settings > Code and each integration's own toggle; you can also request a review on demand by commenting @Sazabi review on a pull request.
See Set up automated code review for the full setup and behavior.
Ask the agent from a pull request
A forge is also an agent surface — a place you can start an agent thread and read its response without leaving the tool. Mention @Sazabi in a pull request comment with any request ("why did this test start failing?", "summarize the risk in this change") and the agent investigates using your connected repositories and project data, then replies in the same comment thread. Keep mentioning it to continue the conversation.
This is separate from automated code review: review runs on its own, while here you drive the questions. See GitHub or Bitbucket for the per-forge details.