Pull Requests & Review
When development is complete, the developer creates a PR from the Konductro UI or CLI. Reviewer assignment is automatic — no chasing people to ask who is available.
Creating a Pull Request
There are two ways to create a PR:
From the UI — click Create PR on the task detail view. Konductro creates the PR on the git provider with the title, description, and acceptance criteria checklist populated automatically.
From the CLI — run the create_pr tool in Claude Code or Amazon Q:
create_pr TICKET-KEYBoth methods produce the same result: a PR on Azure DevOps or Gitea with full context attached.
Automatic Reviewer Assignment
Konductro assigns a reviewer automatically based on the project's review mode:
| Mode | How it works |
|---|---|
| Load balance | Assigns the reviewer with the fewest active reviews. Distributes work evenly across the team. |
| Mapped | Each developer has a configured default reviewer (e.g. Morne's PRs always go to Tiaan). Falls back to load balance if the mapped reviewer is overloaded. |
The assigned reviewer is:
- Added to the PR on the git provider
- Notified via Teams DM (if configured)
- Shown on the task detail and sprint board
PR Lifecycle
| Status | What happened |
|---|---|
pr_open | PR created, reviewer assigned, awaiting review |
merged | PR approved and merged — triggers transition to QA |
When a PR is merged, the task automatically transitions to Internal QA. No manual status update needed.
Review Rules Configuration
Project settings control how reviews work:
- Review mode — load balance or mapped
- Overload threshold — maximum active reviews per person before fallback
- Default reviewer — per-developer mapping (mapped mode only)
- Reviewer eligibility — team members marked as
canReviewin project settings
The PR author is always excluded from the reviewer pool.