Activity and Checks
Inspect pull request activity and build checks.
Global options available on all PR commands: --json [fields], --jq <expression>, --no-color, -w, --workspace, -r, --repo.
bb pr activity
Section titled “bb pr activity”Show a pull request activity log.
bb pr activity <id> [options]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
id |
Pull request ID |
Options
Section titled “Options”| Option | Description | Default |
|---|---|---|
--limit <number> |
Maximum number of activity entries | 25 |
--all |
Show all activity entries (overrides --limit) |
|
--type <types> |
Filter by activity type (comma-separated): comment, approval, changes_requested, merge, decline, commit, update |
|
--no-truncate |
Global flag. Show full details without truncation | |
-w, --workspace <workspace> |
Workspace | |
-r, --repo <repo> |
Repository | |
--json |
Output as JSON |
Examples
Section titled “Examples”# View activity for PR #42bb pr activity 42
# Filter to comment and approval eventsbb pr activity 42 --type comment,approval
# Limit resultsbb pr activity 42 --limit 10
# Show the full activity historybb pr activity 42 --all
# Get activity as JSONbb pr activity 42 --jsonOutput:
TYPE ACTOR DATE DETAILS-------- -------- ------------------------ --------------------------------UPDATE Sam Ali Jul 29, 2026 at 01:20 PM state: OPENCOMMENT Jane Doe Jul 29, 2026 at 10:41 AM #486513002 Why was this removed?APPROVAL Lee Park Jul 28, 2026 at 06:05 PM approvedCOMMIT Sam Ali Jul 28, 2026 at 05:58 PM commit a1b2c3d- Comment snippets and change-request reasons are truncated to 80 characters, and
title:change details to 60. Use--no-truncatefor the full text - An unrecognized
--typetoken fails with--type must be one of: comment, approval, changes_requested, merge, decline, commit, update. Each bad token that is close to a valid one adds a(Did you mean ...?)line; tokens with no close match add nothing --limitis enforced across paginated activity responses- When the result is capped by
--limit, a hint shows how many were listed; use a higher--limitor--allto see the rest (suppressed with--json)
bb pr checks
Section titled “bb pr checks”Show CI/CD checks and build status for a pull request.
bb pr checks <id> [options]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
id |
Pull request ID |
Options
Section titled “Options”| Option | Description |
|---|---|
--no-truncate |
Global flag. Show full check descriptions without truncation |
-w, --workspace <workspace> |
Workspace |
-r, --repo <repo> |
Repository |
--json |
Output as JSON |
Examples
Section titled “Examples”# View checks for PR #42bb pr checks 42
# View checks in a specific repositorybb pr checks 42 -w myworkspace -r myrepo
# Get checks as JSONbb pr checks 42 --jsonOutput:
Pull Request #42 - 3 checks────────────────────────────────────────────────────────────STATUS NAME DESCRIPTION UPDATED----------- -------------- ----------------------------- ------------------------OK passed build Build succeeded in 2m 11s Jul 29, 2026 at 01:31 PMFAIL failed unit-tests 3 of 412 tests failed Jul 29, 2026 at 01:34 PMRUN running deploy-preview Deploying preview environment Jul 29, 2026 at 01:36 PM
OK 1 successful, FAIL 1 failed, RUN 1 pending- The
STATUScell is an icon plus a label:OK passed,FAIL failed,RUN running,STOP stopped, or?plus the raw state for anything else - The summary line counts only successful, failed, and running checks, so it can total fewer than the header count
- Check descriptions are truncated to 40 characters in the table view. Use
--no-truncatefor the full text bb pr checksis not paginated — it makes a single request and has no--limitor--all--jsonreturns{ pullRequestId, workspace, repoSlug, summary, statuses }. Unlike list commands, there is nocountkey — use the length ofstatuses- With no checks, the command prints
No CI/CD checks found for this pull request; with--jsonit returns an emptystatusesarray