@proggarapsody/bitbottle 1.14.3 → 1.16.0

package/README.md

@@ -76,9 +76,10 @@ 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` `ready` `request-review` `comment` |
-| `repo` | `list` `view` `create` `delete` `clone` `set-default` |
+| `repo` | `list` `view` `create` `delete` `clone` `set-default` `rename` `fork` _(Cloud)_ |
 | `branch` | `list` `create` `delete` `checkout` |
 | `tag` | `list` `create` `delete` |
+| `webhook` | `list` `view` `create` `delete` |
 | `commit` | `log` `view` |
 | `pipeline` | `list` `view` `run` _(Cloud only)_ |
 | `api` | Raw REST passthrough with pagination, `--jq`, variable expansion |
@@ -129,11 +130,72 @@ bitbottle branch delete MYPROJ/my-service feature/x
 ### Pipelines _(Cloud only)_
 
 ```bash
-bitbottle pipeline list MYWORKSPACE/my-service
-bitbottle pipeline run  MYWORKSPACE/my-service --branch main
-bitbottle pipeline view MYWORKSPACE/my-service {uuid} --web
+bitbottle pipeline list  MYWORKSPACE/my-service
+bitbottle pipeline run   MYWORKSPACE/my-service --branch main
+bitbottle pipeline view  MYWORKSPACE/my-service {uuid} --web
+
+# Drill into a run:
+bitbottle pipeline steps MYWORKSPACE/my-service {pipeline-uuid}
+bitbottle pipeline logs  MYWORKSPACE/my-service {pipeline-uuid} {step-uuid}
+
+# Repository-level pipeline variables (upsert by KEY):
+bitbottle pipeline variable list   MYWORKSPACE/my-service
+bitbottle pipeline variable set    MYWORKSPACE/my-service DEPLOY_ENV prod
+echo "$TOKEN" | bitbottle pipeline variable set MYWORKSPACE/my-service \
+  API_TOKEN --body=- --secured
+bitbottle pipeline variable delete MYWORKSPACE/my-service DEPLOY_ENV --confirm
 ```
 
+Secured variables redact their value on read (TTY column shows
+`<secured>`, JSON `value` shows `"<secured>"`). Use `--body=-` to read
+the value from stdin so the secret never touches shell history.
+
+### Webhooks
+
+```bash
+bitbottle webhook list   MYPROJ/my-service
+bitbottle webhook view   MYPROJ/my-service {id}
+
+# Create
+bitbottle webhook create MYPROJ/my-service \
+  --url https://hooks.example.com/bb \
+  --events 'repo:push,pullrequest:created'
+
+# With shared secret from stdin (keeps secret out of shell history)
+echo "$WEBHOOK_SECRET" | bitbottle webhook create MYPROJ/my-service \
+  --url https://hooks.example.com/bb \
+  --events 'repo:push' \
+  --secret -
+
+# Delete (destructive — --confirm required when not interactive)
+bitbottle webhook delete MYPROJ/my-service {id} --confirm
+```
+
+Event keys differ between backends:
+- **Cloud** uses `repo:push`, `pullrequest:created`, `pullrequest:approved`, …
+- **Server/DC** uses `repo:refs_changed`, `pr:opened`, `pr:merged`, …
+
+`--secret` accepts the raw value, `-` to read from stdin, or `@PATH` to read
+from a file. Trailing newlines from stdin / file are trimmed. Webhook
+secrets are write-only — neither backend returns them on read.
+
+### Repo extras
+
+```bash
+# Rename (both backends — slug derives from new name on Cloud).
+# --confirm is required on non-TTY because the slug change breaks existing
+# clones' origin URL — run `git remote set-url origin ...` after.
+bitbottle repo rename MYPROJ/my-service my-service-v2 --confirm
+
+# Fork into another workspace (Bitbucket Cloud only)
+bitbottle repo fork myworkspace/my-service --into otherws
+bitbottle repo fork myworkspace/my-service --into otherws --name my-fork
+```
+
+`repo fork` returns a typed unsupported-capability error on Bitbucket Server /
+Data Center, which has no fork primitive in its REST API. Both `rename` and
+`fork` accept `--json fields` and `--jq expr` for structured output.
+
 ### Raw API
 
 ```bash

package/package.json

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