@proggarapsody/bitbottle 1.21.0 → 1.23.0

package/README.md

@@ -76,7 +76,7 @@ Credentials are stored in `~/.config/bitbottle/hosts.yml`. Inside a git repo wit
 |---|---|
 | `auth` | `login` `logout` `status` `token` `refresh` |
 | `pr` | `list` `view` `create` `merge` `approve` `unapprove` `diff` `checkout` `edit` `decline` `reopen` `ready` `request-review` `comment` |
-| `repo` | `list` `view` `create` `delete` `clone` `set-default` `rename` `fork` _(Cloud)_ |
+| `repo` | `list` `view` `create` `delete` `clone` `set-default` `rename` `fork` _(Cloud)_ `file get` `tree` |
 | `branch` | `list` `create` `delete` `checkout` |
 | `tag` | `list` `create` `delete` |
 | `webhook` | `list` `view` `create` `delete` |
@@ -84,7 +84,7 @@ Credentials are stored in `~/.config/bitbottle/hosts.yml`. Inside a git repo wit
 | `pipeline` | `list` `view` `run` _(Cloud only)_ |
 | `workspace` | `list` _(Cloud only)_ |
 | `project` | `list WORKSPACE` _(Cloud only)_ |
-| `issue` | `list` `view` `create` `close` _(Cloud only)_ |
+| `issue` | `list` `view` `create` `close` `edit` `reopen` `assign` `comment {list\|add\|edit\|delete}` _(Cloud only)_ |
 | `search` | `code QUERY` _(Cloud only)_ |
 | `api` | Raw REST passthrough with pagination, `--jq`, variable expansion |
 | `alias` | Custom command shortcuts |
@@ -122,6 +122,11 @@ bitbottle pr request-review 42 --reviewer alice --reviewer bob
 # Decline / reopen (reopen is Bitbucket Server / DC only)
 bitbottle pr decline 42
 bitbottle pr reopen  42
+
+# Read review comments — general + inline (file:line) anchors and replies
+bitbottle pr comment list 42                            # all comments; LOCATION column shows path:line for inline
+bitbottle pr comment list 42 --inline                   # only inline review comments
+bitbottle pr comment list 42 --json id,inline,parentId,resolved,updatedAt
 ```
 
 ### Repos & Branches
@@ -223,6 +228,33 @@ bitbottle repo fork myworkspace/my-service --into otherws --name my-fork
 Data Center, which has no fork primitive in its REST API. Both `rename` and
 `fork` accept `--json fields` and `--jq expr` for structured output.
 
+### Reading source at a ref
+
+Read file content and directory listings at any ref (branch, tag, commit
+hash) without cloning. Both backends; the bytes round-trip cleanly so
+binary files survive `--out`.
+
+```bash
+# Read a file at a ref — straight to stdout
+bitbottle repo file get MYPROJ/my-service README.md --ref main
+
+# Pin a tag and write to disk (binary-safe)
+bitbottle repo file get MYPROJ/my-service logo.png --ref v1.2.0 --out logo.png
+
+# List a directory at a ref. PATH defaults to the repo root.
+bitbottle repo tree MYPROJ/my-service --ref main
+bitbottle repo tree MYPROJ/my-service cmd --ref main
+
+# Structured output for scripts and agents
+bitbottle repo tree MYPROJ/my-service --ref main --json path,type,size
+bitbottle repo tree MYPROJ/my-service --ref main --jq '.[]|select(.type=="dir").path'
+```
+
+`type` is normalised to `file` or `dir` across both backends. Submodules
+surface as `dir` (with the submodule pointer in `hash`) so renderers can
+recurse uniformly without a special case. The MCP equivalents are
+`get_file_content` and `list_tree`.
+
 ### Workspaces & Projects (Cloud only)
 
 ```bash
@@ -260,6 +292,70 @@ runs. Bitbucket Server / Data Center has no first-class code-search
 REST endpoint; invocations against a Server host return the typed
 `host.unsupported` error.
 
+### Code Insights _(Bitbucket Server / DC only)_
+
+Post build / quality / security analysis results as structured annotations
+on commits. Requires Bitbucket Server / Data Center.
+
+```bash
+# Create or update a report (upsert by key)
+bitbottle --hostname git.example.com code-insights report set \
+  MYPROJ/my-service abc123def456 my-scanner \
+  --title "Security Scan" --result PASS \
+  --report-type SECURITY --reporter "semgrep"
+
+# List all reports for a commit
+bitbottle --hostname git.example.com code-insights report list \
+  MYPROJ/my-service abc123def456
+
+# View a single report as JSON
+bitbottle --hostname git.example.com code-insights report view \
+  MYPROJ/my-service abc123def456 my-scanner \
+  --json key,title,result,details
+
+# Bulk-add annotations from a JSON file
+bitbottle --hostname git.example.com code-insights annotation add \
+  MYPROJ/my-service abc123def456 my-scanner \
+  --from-json @findings.json
+
+# Single annotation
+bitbottle --hostname git.example.com code-insights annotation add \
+  MYPROJ/my-service abc123def456 my-scanner \
+  --path src/main.go --line 42 --severity HIGH --type BUG \
+  --message "Potential null dereference"
+
+# List annotations for a report
+bitbottle --hostname git.example.com code-insights annotation list \
+  MYPROJ/my-service abc123def456 my-scanner --json path,severity,message
+
+# Delete a report and all its annotations
+bitbottle --hostname git.example.com code-insights report delete \
+  MYPROJ/my-service abc123def456 my-scanner
+```
+
+#### Merge checks (experimental)
+
+Configure a Code Insights report as a required gate for PR merges. The
+underlying API is partly undocumented — commands are marked experimental.
+
+```bash
+# Require the "my-scanner" report to pass before merging
+bitbottle --hostname git.example.com code-insights merge-check set \
+  MYPROJ/my-service required-scan \
+  --report-key my-scanner --must-pass --min-severity MEDIUM
+
+# Inspect the current merge-check configuration
+bitbottle --hostname git.example.com code-insights merge-check get \
+  MYPROJ/my-service required-scan
+
+# Remove the merge check
+bitbottle --hostname git.example.com code-insights merge-check delete \
+  MYPROJ/my-service required-scan
+```
+
+Invoking any `code-insights` command against a Bitbucket Cloud host returns
+the typed `host.unsupported` error.
+
 ### Raw API
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proggarapsody/bitbottle",
-  "version": "1.21.0",
+  "version": "1.23.0",
   "description": "Bitbucket CLI for Server/Data Center and Cloud — npm wrapper for bitbottle",
   "keywords": [
     "mcp",