Skip to main content

The list, filters, and rules

The header​

  • A project selector: the list always belongs to one project at a time.
  • Rules: opens the rules dialog (below).
  • Refresh: re-fetches the list; the icon spins while loading. If a refresh fails, you will see "Refresh failed. Showing the last successful results." and the previous list stays on screen.

How do I filter and sort?​

Below the header, the filter bar offers:

  • A search box (matches by title)
  • All repositories dropdown, listing every repository connected to the project
  • All providers dropdown (GitHub / GitLab)
  • All states dropdown (Open / Merged / Closed)
  • Author (free text)
  • Branch (free text)
  • Created from / Created to date pickers
  • Linked to issue checkbox: only pull requests already linked to a card
  • A sort dropdown: Recently updated, Newest, Oldest, or Title A–Z
  • Clear: resets every filter to its default

The default view is Open pull requests, sorted by most recently updated.

The table​

Each row shows: the pull request's number and title; source → target branch; whether it is linked to a card or still a draft; the repository (with a provider badge and an OAuth or PAT connection badge); the author; its status; and when it was last updated. A merge icon appears next to the status once a pull request has been merged. Click any row to open its review page.

Above the table, a count line reads {n} pull requests (with a "· refreshing…" suffix while a background fetch is in flight), and Previous / Next buttons with a Page X of Y label page through longer lists.

Empty state: "No pull requests match the current filters. Try refreshing or widen the filters."

Connection errors: if one or more connected repositories cannot be reached, a warning banner reads {n} repositories could not be loaded from the provider, with a note: "This usually means the connected token or account lost access. Check the integration's token scope and lifetime, then reconnect the account." The rest of the list still loads normally for repositories that did respond.

Rules​

Click Rules to open Pull request rules, configured per connected repository: "Choose what reaches communication channels and when ACE analyzes a pull request. Posting and analysis are independent; target branches scope both enabled behaviors."

For each repository:

  • Post to communication channels: whether opening or continuing this pull request's discussion thread is also posted into your connected communication channels (needs a channel set up for the project; the dialog links to Manage channels → if you do not have one yet).
  • Analyze automatically: whether the agent automatically runs a code analysis whenever a pull request opens or changes, on a matching target branch.
  • Target branches: a comma-separated list (for example, main, release/*) that scopes both of the toggles above, not just analysis. It is editable as soon as either toggle is on, and disabled only when both are off. Leave it empty to match every target branch.

If no repository is connected yet, the dialog shows "Connect a repository to create pull request rules." instead of the form.

Click Save rules to apply your changes. If you do not have permission to change rules (missing repo:manage), every toggle is disabled and the button reads Close instead of Cancel.

On this page