@proggarapsody/bitbottle 1.50.0 → 1.52.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +21 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -90,6 +90,7 @@ Tokens are intentionally stripped from `hosts.yml` on every save. If you have an
|
|
|
90
90
|
| `tag` | `list` `create` `delete` |
|
|
91
91
|
| `webhook` | `list` `view` `create` `delete` |
|
|
92
92
|
| `deploy-key` | `list` `add` `delete` |
|
|
93
|
+
| `ssh-key` | `list` `add` `delete` _(Cloud only)_ |
|
|
93
94
|
| `commit` | `log` `view` `status` `comment {list\|add\|edit\|delete}` |
|
|
94
95
|
| `pipeline` | `list` `view` `run` _(Cloud only)_ |
|
|
95
96
|
| `deployment` | `list` `view` _(Cloud only)_ |
|
|
@@ -295,6 +296,21 @@ bitbottle deploy-key delete MYPROJ/my-service 42
|
|
|
295
296
|
All three subcommands work on both Bitbucket Cloud and Server/DC. `list` and
|
|
296
297
|
`add` support `--json` / `--jq` / `--yaml` for structured output.
|
|
297
298
|
|
|
299
|
+
### SSH keys (Cloud only)
|
|
300
|
+
|
|
301
|
+
```bash
|
|
302
|
+
# List SSH keys for the current user
|
|
303
|
+
bitbottle ssh-key list
|
|
304
|
+
|
|
305
|
+
# Add an SSH key
|
|
306
|
+
bitbottle ssh-key add --key "ssh-rsa AAAA..." --label "Laptop"
|
|
307
|
+
|
|
308
|
+
# Delete an SSH key by ID
|
|
309
|
+
bitbottle ssh-key delete 42
|
|
310
|
+
```
|
|
311
|
+
|
|
312
|
+
`list` and `add` support `--json` / `--jq` / `--yaml` for structured output.
|
|
313
|
+
|
|
298
314
|
### PR default reviewers
|
|
299
315
|
|
|
300
316
|
```bash
|
|
@@ -321,11 +337,16 @@ bitbottle repo rename MYPROJ/my-service my-service-v2 --confirm
|
|
|
321
337
|
# Fork into another workspace (Bitbucket Cloud only)
|
|
322
338
|
bitbottle repo fork myworkspace/my-service --into otherws
|
|
323
339
|
bitbottle repo fork myworkspace/my-service --into otherws --name my-fork
|
|
340
|
+
|
|
341
|
+
# Transfer to another project (Server) or workspace (Cloud)
|
|
342
|
+
bitbottle repo transfer MYPROJ/my-service --to NEWPROJ
|
|
343
|
+
bitbottle repo transfer myworkspace/my-service --to otherws
|
|
324
344
|
```
|
|
325
345
|
|
|
326
346
|
`repo fork` returns a typed unsupported-capability error on Bitbucket Server /
|
|
327
347
|
Data Center, which has no fork primitive in its REST API. Both `rename` and
|
|
328
348
|
`fork` accept `--json fields` and `--jq expr` for structured output.
|
|
349
|
+
`repo transfer` works on both backends and also accepts `--json`/`--jq`.
|
|
329
350
|
|
|
330
351
|
### Reading source at a ref
|
|
331
352
|
|