Skip to main content

Issues and Pull Requests

Reading a forge from inside Daintree: the repository stats toolbar, the issues and pull-requests panel, filtering and search, CI status, review state, and commit-author avatars.

Updated
Reviewed

Repo stats toolbar

With a forge connected, the toolbar shows live counts for the active project in one grouped control:

  • Open issues on the repository
  • Open pull requests (open merge requests on GitLab)
  • Commits on the branch the project root has checked out

The commits count is local git data, so it stays even in a project with no forge at all. The issue and pull request counts are forge data and appear only when a provider resolves for the project.

The counts are real totals, not a capped "20+". A + suffix appears only when the number genuinely is approximate, which happens when a cached list is serving the count and no real total came with it. Two sources feed each count (the periodic stats poll and the count the dropdown list reports when it loads), and whichever was read more recently wins, so the badge can't freeze on a stale list count.

Click a count to open its dropdown panel. On GitLab the issue and merge request counts open the project's pages in your browser instead; see On GitLab. A project whose issues come from an issue tracker works the same way for its issues count; see With an issue tracker. On a narrow toolbar the stats move into the ··· overflow menu.

Right-click a count for its own navigation first: View all issues on GitHub, View all pull requests on GitHub, or View commits on GitHub for the active branch, then View repository on GitHub (GitLab's name on a GitLab project). Below those sit Customize toolbar… and Unpin from toolbar. Once the stats are unpinned, the way back is right-clicking empty toolbar space or Customize toolbar….

Freshness

Each count's tooltip and accessible name say how current it is, so you know whether you're looking at fresh data or a cached snapshot:

  • Fresh (under 90 seconds old, three times the active poll): no extra note.
  • Aging: a note like · updated 3m ago.
  • Cached from previous session: shown right after launch, before the first live refresh lands.
  • Couldn't refresh: the last known counts stay on screen with that note. If failures keep coming past the quick retries, a warning mark joins the control, and its tooltip names the error.

Hovering a count warms its dropdown in the background, so the panel is ready by the time you click. If the cached data is recent enough, Daintree skips the prefetch.

Activity chip

When a count goes up while its dropdown is closed, Daintree flags the new activity. A small chip appears in the corner of the count, and the number animates as it changes. It's a glance-able cue that something arrived, not a literal "+N" badge and not an unread counter. The chip clears on its own three minutes after the latest increase, or as soon as you open that dropdown.

How often counts refresh

Four things drive the refresh cadence, and they compose rather than replace each other:

  • Base cadence. Every 30 seconds while the app is in front of you, backing off to every 5 minutes in the background.
  • The provider's own hint. Each poll can report an adaptive cadence (faster on a busy repo, slower on a quiet one) clamped to that same 30-second-to-5-minute range so a bad hint can't hammer the API or stall the counts.
  • Rate-limit health. When a provider is running low on quota, the background interval is multiplied out to give it room to recover.
  • Local git signals. A local ref moving the ahead count, or the origin count moving against you, enqueues a debounced recheck within about a second. This is what makes a commit or a fetch reflect in the toolbar immediately rather than at the next scheduled poll.

Errors get graduated backoff: the first failure retries in 30 seconds so a blip heals fast, doubling toward a two-minute ceiling for something that keeps failing. Waking your machine from sleep triggers an immediate refresh.

Rate limits

If the forge starts rate-limiting requests, a clock glyph joins the control. Hover or focus it for a per-bucket breakdown: how many requests remain in each rate-limit bucket, each with a live countdown to its reset. Reading the breakdown doesn't itself cost any quota. When a reset time is known, the next poll is scheduled just past it rather than on the normal cadence.

Commits dropdown

The commits count opens a searchable list of the active worktree's branch history. Commits that haven't reached the branch's push destination are marked Not pushed, and the footer sums them up (for example 2 not pushed to origin/feature/x), or says plainly that there is nothing to push or that the destination couldn't be checked. Press Enter on a commit to expand its message body, or to copy its hash when it has none. On a GitHub project the footer adds View on GitHub.

Issues and PR panel

On GitHub, clicking the issue or pull request count opens a dropdown panel with the search input focused, so you can start typing right away.

State tabs at the top narrow the list. Issues show Open and Closed. Pull requests show Open, Merged, and Closed. The search field also takes number-based patterns for quick lookups:

PatternFetches
#42 or 42A single issue or PR by number.
42, 45, 51 or 42 45 and 51Several specific items, separated by commas, spaces or a lowercase and. Duplicates are collapsed, and a pasted list with a trailing comma still works.
42..50An inclusive range. The separator is two dots: a hyphen matches nothing.
42+An open-ended range from that number onwards.

Lists and ranges are capped at 20 items, counted from the start. A result banner above the list says exactly what you're looking at: Showing issue #42, Showing #42, #45, #51, Showing range #42..#50, Showing first 20 of range #42..#90 (capped), or Showing #42 and above. A number that isn't in the current tab reads No issue #42 in this view. When a query looks like a number list but doesn't parse, the panel says it is showing text matches and suggests separating the numbers with commas or spaces.

At the bottom, View on GitHub opens the filtered list in your browser, and New issue or New pull request opens GitHub's create page. Once the list is more than five minutes old, an Updated line sits between them; before that, the refresh button beside the search field says when it last updated in its tooltip.

Instant open and caching

When a recent disk cache exists, the panel can show the previous session’s first page immediately on launch. Without a usable cache, it loads results from the provider. That cache has a 10-minute freshness budget: anything older is dropped on read rather than shown, and the first live poll overwrites it within seconds anyway.

Within a session, reopening the panel shows recently cached results from memory while a background refresh runs quietly. The in-session cache is keyed by project, resource type, filter state, and sort order, so switching any of those triggers a fresh fetch. Search results always fetch live and aren't cached.

Persistent panel state

The panel stays mounted between opens, so within a session the state tab and sort order you chose are still there when you reopen it, and so is a selection you started (see Selecting items). The search text is the exception: closing the panel clears it.

Keyboard navigation

The panel can be driven entirely from the keyboard. Focus stays in the search field while the arrow keys move a highlight through the rows:

  • ↑ / ↓ moves through the list
  • Enter runs the row's own action: switch to its worktree if one exists, create a worktree for an open item, or open a closed issue or merged PR in your browser
  • Command-Enter Control-Enter Control-Enter opens the highlighted item in your browser
  • Shift+Space selects or deselects the highlighted row; a bare Space stays in the search text
  • Shift+F10 or the Menu key opens the row's actions menu
  • Escape clears the selection first, then the search text, then closes the panel

Sort order

A sort button next to the search field offers two options:

  • Newest (default): sorts by creation date, matching GitHub.com's default order
  • Recently updated: sorts by last activity

The button's tooltip reads Sort: recently updated while that order is active. The choice applies to both the browse list and typed search results, and it's tracked separately for issues and PRs. Each row's age follows the sort: creation time under Newest, last update under Recently updated.

Note
Sort order is session-only. It resets to "Newest" when you restart Daintree.
Browse open issues with their labels, linked pull requests and row actions
Browse merged pull requests, or change the state filter

Row details

Each row uses a two-line layout that keeps the key information visible at a glance:

  • Title line: state icon, title, then a fixed rail on the right with the CI or merge-conflict mark (open PRs only), the first assignee's avatar (with +N for more) and the ··· actions menu
  • Metadata line: the #number (click to copy it), Worktree or Current when a local worktree exists for the item, the review decision on PRs (Approved or Changes requested), author, age, comment count, then the head branch (PRs) or the linked PR and the first label with a +N count (issues)

Clicking the title opens the item on GitHub. Clicking anywhere else on the row runs the same action as Enter. An issue's linked-PR chip shows the PR's number with its own CI or conflict mark, and clicking it opens that PR.

The ··· menu leads with the row's own action: Switch to worktree when a worktree exists (and isn't the one you're in), or Create worktree for an open item without one. Then come Open on GitHub, Copy number, Open pull request #N for an issue with a linked PR, and Select or Deselect.

CI status icons

Open PR rows show a status mark in the rail beside the title:

  • Green check: checks passing (tooltip All checks passed)
  • Amber dot: checks pending (Checks pending)
  • Red X: checks failing (Checks failing)
  • Merge-conflict mark: the PR conflicts with its base branch. It takes the slot over any CI result, because GitHub skips pull_request workflows until the conflict is resolved, and a conflicting PR otherwise looks as if CI never ran.

The status is derived from the repository's required checks rather than the raw rollup, so an optional job doesn't turn a mergeable PR red. Daintree falls back to the raw rollup in the cases where filtering to required checks would be a guess: the contexts page came back truncated, the contexts list is missing entirely, no required contexts are present (a repository without branch protection), or a required check reports a state Daintree can't classify. Falling back is deliberate: a false green on a truncated page is worse than an unfiltered status. If the PR has no checks at all, no mark appears.

To see the individual checks behind a mark, open the PR's worktree in Review Hub and click its PR chip.

When the forge is unreachable

The panel degrades rather than going blank. When a refresh fails or requests are paused, it keeps showing the last results it fetched, with an inline banner:

  • Rate-limited: GitHub paused requests. Showing saved results, with a live countdown to when they resume.
  • Network error: Couldn't reach GitHub. Showing saved results, with a Retry button.
  • Token error: the error itself, with a Settings button instead of Retry.

With nothing cached to show, the same causes fill the panel instead: GitHub requests are paused with the time they resume, Couldn't reach GitHub with Retry, or GitHub rejected the token with Open GitHub settings. With no token stored at all, the panel reads GitHub not connected with an Add GitHub token button that takes you to the provider's section in settings.

On GitLab

A GitLab project gets the toolbar counts for open issues and open merge requests, with the same freshness notes, activity chip, refresh cadence and rate-limit breakdown. The GitLab provider contributes no dropdown panel, so clicking either count opens the project's issues or merge requests page in your browser, and hovering does not prefetch anything. The commits dropdown works as it does everywhere, from local git.

Merge requests still reach the rest of Daintree. A worktree whose branch has a merge request shows its badge, the Review Hub chip shows the head pipeline's status, and agents can read issues, merge requests, CI status and conflict state through the forge.* actions.

With an issue tracker

A project can take its issues from Jira, Linear or Beads through Issues provider in Project settings. As long as a code forge also resolves for the project, the issues count is then the tracker's open count, and its tooltip and right-click menu name the tracker, as in View all issues on Linear. None of the trackers has a dropdown panel, so clicking the count opens the tracker's issue list in your browser, or the tracker's settings when Daintree recognizes a missing or rejected credential. Beads has no web pages, so there it has nothing to open.

The pull request count stays with the code forge, and so does what clicking it opens. Without the issues panel there is no issue selection to start bulk worktree creation from; pick a tracker issue in the Create worktree dialog instead, as From an issue tracker describes.

Commit-author avatars

Commit-author avatars on worktree cards resolve through whichever forge provider is active for that project, rather than being hardcoded to GitHub. Daintree picks an avatar in this order:

  1. A branded icon when the author is an AI agent
  2. The author's profile picture from the active forge provider
  3. A Gravatar match for the commit email
  4. Deterministic colored initials when nothing else resolves

Both built-in providers resolve profile pictures: GitHub from the account behind the commit, GitLab from the instance's avatar lookup for the commit email.