@proggarapsody/bitbottle 1.21.0 → 1.22.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` |
@@ -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

package/package.json

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