Skip to main content

Pull Requests

Software Factory → Pull Requests lists pull requests pulled live from every repository connected to the current project, whether GitHub or GitLab, and whether the connection uses OAuth or a personal access token. The list is fetched fresh every time you open or refresh the page. There is no separate sync step, and (unlike Deployments) nothing here refreshes itself automatically, so use Refresh to pull new results.

This is where you find and review a pull request. Turning one into tracked work, or jumping from it into Chat, is covered here from the pull request's own side. The matching entry on a card (a "Pull Requests" section in its sidebar, plus its own "Discuss in chat" and checkpoint flow) is covered in the Development guide.

In this section​

  • The list, filters, and rules: the pull request table, every filter, pagination, connection-error banners, and the per-repository Rules dialog (auto-posting to chat, automatic analysis).
  • Reviewing a pull request: the review page, covering linking or creating a card, the Files/Analysis/History views, the Summary panel, and the Approve/Reject/Merge decisions.

Where to find it​

  • See pull requests: left sidebar → Software Factory → Pull Requests, or go straight to /software-factory/pull-requests. It is a per-project view, so pick the project with the selector at the top of the page.
  • Jump to a pull request from a card: the Pull Requests section in a card's sidebar (see The issue detail page) links out to the matching row on this screen.

Who can do this?​

  • pr:read: see the list and open a pull request's review page.
  • pr:review: approve or reject a pull request, and run or re-run its analysis.
  • pr:merge: see and use the Merge button (a separate grant from review, so someone can approve without being able to merge).
  • issue:create / issue:read: create a card from a pull request, or see and unlink an already-linked one.
  • chat:access: use Discuss in chat.
  • repo:manage: open the Rules dialog and change its settings (without it, Rules is still viewable but every toggle is disabled and the button reads Close).

None of the decision buttons work on an archived or otherwise non-mutable project, regardless of role; the project's own lifecycle state overrides any permission grant.

On this page