Pull request Kanban board

A Kanban board for your GitHub pull requests

A list of PRs tells you what is open. A board tells you where each one is stuck. PRLane places every pull request across your repositories in a lane by merge readiness, so the team can see at a glance what needs review, what is blocked, and what is ready to land.

Waiting Review2
  • Add audit log export
    #812claude
  • Cache repo settings
    #806maya
Conflicts1
  • Split billing service
    #799codex
Ready to Merge3
  • Fix flaky login test
    #815cursor
  • Bump eslint config
    #810dev
  • Retry webhook delivery
    #804claude

Lanes by merge readiness

Draft, blocked, conflicts, waiting review, ready to merge, queued, merged, and closed.

Columns you define

Add, rename, reorder, or hide columns, and filter a column by repository or workspace.

Act from the card

Merge, open the preview, or check CI on a card without leaving the board.

01

Every PR in the lane that matches its state

PRLane sorts pull requests into lanes from their live GitHub state: drafts, PRs blocked with CI still running or failing, PRs blocked with CI passing, merge conflicts, waiting for review, ready to merge, queued or merging, merged, and closed. Cards move on their own as checks finish, reviews land, and branches change.

02

Build the board your team works from

The default lanes are a starting point. Add a column for one repository or workspace, rename lanes to match your process, reorder them, and hide a column when it is empty. Choose what each card shows, such as the author, merge readiness, review state, checks, conflicts, risk, size, open threads, CI cost, and GitHub and preview links.

03

Clear a whole lane at once

When the ready lane fills up, select it and merge or queue every PR in it from the bulk bar. Select the conflicts lane to update branches with main, or hand the whole lane to a coding agent with the fix context for each PR.

04

People and agents on the same board

Pull requests from Claude Code, Codex, Cursor, and other agents appear next to your team's, with the author on each card. Reviewers see one queue instead of one per tool, and managers can see which lane is backing up before it delays a release.

Common questions

Do I have to move cards by hand?

No. Lanes come from each PR's state on GitHub, so cards move when checks, reviews, conflicts, or merges change.

Can one board show several repositories?

Yes. The board covers every repository in your workspace, and you can add columns that show only one repository or workspace.

Is there a table view too?

Yes. The same fleet is available as a table and as cards, with the same filters, so each person can work in the view they prefer.

Further reading

More from PRLane

Get your PR fleet under control

Connect GitHub, see every open pull request across your repositories, and start merging the ready ones. The Free plan has no monthly fee.