@proggarapsody/bitbottle 1.51.0 → 1.53.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 +24 -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
|
+
| `branch-rule` | `list` `add` `delete` _(Cloud only)_ |
|
|
93
94
|
| `ssh-key` | `list` `add` `delete` _(Cloud only)_ |
|
|
94
95
|
| `commit` | `log` `view` `status` `comment {list\|add\|edit\|delete}` |
|
|
95
96
|
| `pipeline` | `list` `view` `run` _(Cloud only)_ |
|
|
@@ -296,6 +297,24 @@ bitbottle deploy-key delete MYPROJ/my-service 42
|
|
|
296
297
|
All three subcommands work on both Bitbucket Cloud and Server/DC. `list` and
|
|
297
298
|
`add` support `--json` / `--jq` / `--yaml` for structured output.
|
|
298
299
|
|
|
300
|
+
### Branch restriction rules (Cloud only)
|
|
301
|
+
|
|
302
|
+
```bash
|
|
303
|
+
# List branch restriction rules
|
|
304
|
+
bitbottle branch-rule list myworkspace/my-service
|
|
305
|
+
|
|
306
|
+
# Add a rule requiring 2 approvals before merging to main
|
|
307
|
+
bitbottle branch-rule add myworkspace/my-service --kind require_approvals_to_merge --pattern main --value 2
|
|
308
|
+
|
|
309
|
+
# Add a push restriction (no direct pushes to main)
|
|
310
|
+
bitbottle branch-rule add myworkspace/my-service --kind push --pattern main
|
|
311
|
+
|
|
312
|
+
# Delete a rule by ID
|
|
313
|
+
bitbottle branch-rule delete myworkspace/my-service 7
|
|
314
|
+
```
|
|
315
|
+
|
|
316
|
+
Cloud only. `list` and `add` support `--json` / `--jq` / `--yaml` for structured output.
|
|
317
|
+
|
|
299
318
|
### SSH keys (Cloud only)
|
|
300
319
|
|
|
301
320
|
```bash
|
|
@@ -337,11 +356,16 @@ bitbottle repo rename MYPROJ/my-service my-service-v2 --confirm
|
|
|
337
356
|
# Fork into another workspace (Bitbucket Cloud only)
|
|
338
357
|
bitbottle repo fork myworkspace/my-service --into otherws
|
|
339
358
|
bitbottle repo fork myworkspace/my-service --into otherws --name my-fork
|
|
359
|
+
|
|
360
|
+
# Transfer to another project (Server) or workspace (Cloud)
|
|
361
|
+
bitbottle repo transfer MYPROJ/my-service --to NEWPROJ
|
|
362
|
+
bitbottle repo transfer myworkspace/my-service --to otherws
|
|
340
363
|
```
|
|
341
364
|
|
|
342
365
|
`repo fork` returns a typed unsupported-capability error on Bitbucket Server /
|
|
343
366
|
Data Center, which has no fork primitive in its REST API. Both `rename` and
|
|
344
367
|
`fork` accept `--json fields` and `--jq expr` for structured output.
|
|
368
|
+
`repo transfer` works on both backends and also accepts `--json`/`--jq`.
|
|
345
369
|
|
|
346
370
|
### Reading source at a ref
|
|
347
371
|
|