Review pull requests
iKAgent → Review lists the open pull requests in your repositories, from people and from agents. You can act on a PR from iKanban, or ask an agent to review it or fix its review comments.
Before you start
-
Connect GitHub in Agent settings → Connections.
-
Make sure your repositories are connected to iKanban. Review shows a repository from any of these sources:
- the iKanban GitHub App installed for your workspace's GitHub organization;
- a GitHub repository linked to a project of a team you are in;
- a repository you linked to your own GitHub connection.
Review does not show every repository on your GitHub account. GitHub still applies your own access: you see and act only where your GitHub account can.
The line under the list says how many repositories are connected, and links to Settings → Connections.
The list
The list has three groups: Needs your review, Opened by agents and Everything else. Filter by repository, team, author or state (open or draft), or paste a PR link in the box above the list.
- A PR shows its iKanban task when an agent opened it for that task, on GitHub or in a session on your laptop runner, or when its title or branch names the task's issue key (for example
IKA-123). The key must belong to a task in a project that has this repository. A PR an agent opened shows under Opened by agents. - The team of a PR comes from, in this order: its task's team; the team of its repository's wiki (see Repository wiki); the team of a project that has this repository. With none of these, the PR shows under No team.
- Each PR shows its checks: passing, failing, running, or none.
Act on a pull request
Open a PR to see its timeline and its actions: mark ready, approve workflows, approve, request changes, merge and close. People's PRs get the same actions as agents' PRs.
iKanban acts with your own GitHub sign-in. GitHub then applies your permissions on that repository. When the PR belongs to a task you can open, iKanban also writes the action as a comment on that task.
Ask an agent
Ask an agent has two choices: Review this PR and Fix the review comments. Each one runs Claude, Copilot or Gemini, on my machine or on GitHub.
Each ask creates a session, and the session opens at its own page.
- My machine: the session runs on your laptop runner, with the PR link and its task.
- GitHub: iKanban posts
@claudeor@geminion the PR, and ties the session to the PR. Claude and Gemini answer only if the repository has their iKanban workflow (see GitHub runs). For Review this PR with Copilot, iKanban requests Copilot as a reviewer of the PR. For Fix the review comments with Copilot, iKanban posts@copilot.
Before an ask goes out, iKanban checks your workspace's AI policy for that agent, on the session's task.
The rules that decide what you see and what runs
These are deliberate. Each one says what you will see, and where to change it.
| Rule | What happens | Where you see it | Change it |
|---|---|---|---|
| Connected repositories only | Review shows PRs only from repositories in the workspace's iKanban GitHub App, linked to a project of your teams, or linked to your GitHub connection. An action on any other repository is refused. | the line under the list: N repositories | Agent settings → Connections (GitHub App, project repositories, GitHub) |
| No GitHub connection | The list is empty. | Connect GitHub in Settings → Connections … | Agent settings → Connections |
| List refreshed every 60 seconds | iKanban keeps your list for 60 seconds, to stay inside GitHub's rate limits. A PR opened on GitHub can take up to a minute to appear. An action you take in iKanban refreshes the list at once. | the list | wait a minute |
| First 50 open PRs per repository | A repository with more than 50 open PRs shows only its 50 most recently updated. | A repository has more than 50 open pull requests; only its 50 most recently updated are listed. | filter by repository; close old PRs |
| Open and draft PRs only | Merged and closed PRs are not listed. | the list | open the PR on GitHub |
| Task link by issue key | A person's PR links to a task only when its title or branch names that task's issue key, and the task's project has this repository. | the task on the PR row | put the issue key in the PR title or branch |
| Team of a PR | The task's team, else the repository's wiki team, else the team of a project that has the repository. With none, it is No team, and a team filter hides it. | the Team filter; No team | give the repository a team on iKAgent → Wiki, or add it to a project |
| No review of your own PR | GitHub does not let the author approve or request changes on a PR. When the PR's author is your GitHub account (the laptop runner pushes as you), Approve and Request changes are off. Merge and close still work. | GitHub does not let you review your own pull request. | ask a teammate to review it on GitHub |
| Your GitHub permissions | Approve, merge and the other actions run as you. If GitHub refuses (no write access, a required review, a failing required check), the action fails with GitHub's message. | the error under the action | your role on the repository |
| API keys | An iKanban API key can call the same PR actions as its owner, as the task PR actions allow. | — | delete the key in Settings → API Keys |
| Sessions land in team IKA | Every ask from Review, on my machine or on GitHub, is a session task in team IKA, project ai-agent, feature AI agents. You must be a member of team IKA. | Agent sessions live in team IKA; switch to its workspace. | a workspace admin adds you to team IKA |
| Workspace AI policy | An ask is refused when the workspace or team policy turns AI, or that agent, off. | AI is disabled by your workspace administrator or Agent is disabled by workspace or team policy | a workspace admin, in Agent settings → Workspace AI controls |
| My machine needs your runner | A session waits while your iKanban app is closed. iKanban tries to start it. | … queued. Starting your local runner… | open the iKanban app |
| Gemini on GitHub, fix | Not offered: Gemini on GitHub works from the default branch and can't push to the PR. | the greyed item, with its reason | use Gemini on my machine |
| Copilot on GitHub, review | iKanban requests Copilot as a reviewer of the PR, on any PR. Copilot posts its review on GitHub. | the PR's reviewers on GitHub | — |
| Copilot on GitHub, fix | Offered only on PRs Copilot opened: Copilot answers @copilot only there. | the greyed item, with its reason | use Copilot on my machine |