Activity and Checks

Inspect pull request activity and build checks.

See Global flags for JSON output, workspace/repository selection, and display options.

bb pr activity

Show a pull request activity log.

bb pr activity [id] [options]

Arguments

Argument	Description
id	Pull request ID (optional, defaults to the open PR for the current branch)

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 instead of fitting them to the terminal

Examples

# View activity for PR #42
bb pr activity 42

# Filter to comment and approval events
bb pr activity 42 --type comment,approval

# Limit results
bb pr activity 42 --limit 10

# Show the full activity history
bb pr activity 42 --all

# Get activity as JSON
bb pr activity 42 --json

Output:

TYPE      ACTOR     DATE         DETAILS
--------  --------  -----------  --------------------------------
UPDATE    Sam Ali   2 hours ago  state: OPEN
COMMENT   Jane Doe  5 hours ago  #486513002 Why was this removed?
APPROVAL  Lee Park  yesterday    approved
COMMIT    Sam Ali   yesterday    commit a1b2c3d

Notes

• Long details are shortened to fit the terminal width. Use --no-truncate for the full text
• An unrecognized --type token 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
• --limit is enforced across paginated activity responses
• When the result is capped by --limit, a hint shows how many were listed; use a higher --limit or --all to see the rest (suppressed with --json)

---

bb pr checks

Show CI/CD checks and build status for a pull request.

bb pr checks [id] [options]

Arguments

Argument	Description
id	Pull request ID (optional, defaults to the open PR for the current branch)

Options

Option	Description
--watch	Wait until no check is in progress; exit non-zero if any failed or stopped
--interval <seconds>	Seconds between polls with --watch (default: 10)
--no-truncate	Global flag. Show full check descriptions without fitting them

Examples

# View checks for PR #42
bb pr checks 42

# View checks in a specific repository
bb pr checks 42 -w myworkspace -r myrepo

# Get checks as JSON
bb pr checks 42 --json

# Wait for running checks, then merge only if none failed
bb pr checks 42 --watch && bb pr merge 42

Output:

Pull Request #42 - 3 checks
────────────────────────────────────────────────────────────
STATUS       NAME            DESCRIPTION                    UPDATED
-----------  --------------  -----------------------------  --------------
OK passed    build           Build succeeded in 2m 11s      5 minutes ago
FAIL failed  unit-tests      3 of 412 tests failed          2 minutes ago
RUN running  deploy-preview  Deploying preview environment  now

OK 1 successful, FAIL 1 failed, RUN 1 pending

With --watch, the command prints Waiting for 1 of 3 checks on pull request #42..., then one line per check whose state changes, then the table above once nothing is running:

Waiting for 1 of 3 checks on pull request #42...
  OK deploy-preview passed

Required checks

--watch only judges the checks Bitbucket reports. When none is listed yet it waits three more polls for the first one, then fails with No checks were reported on pull request #42. A required check that has not started while others finish is still invisible. The auto-merge recipe explains required check keys and merge policies.

Notes

• The STATUS cell 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
• Long check names and descriptions are shortened to fit the terminal width. Use --no-truncate for the full text
• bb pr checks reads every status page, so it has no --limit or --all
• Without --watch the exit status is 0 whatever the checks say. With --watch a failed or stopped check exits 1 with error code 10001 CI_FAILED, after printing the final state; --json prints only that final envelope, no progress lines
• --json returns { pullRequestId, workspace, repoSlug, summary, statuses }. Unlike list commands, there is no count key, use the length of statuses
• With no checks, the command prints No CI/CD checks found for this pull request; with --json it returns an empty statuses array