@proggarapsody/bitbottle 1.15.0 → 1.17.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 +68 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -76,12 +76,15 @@ Credentials are stored in `~/.config/bitbottle/hosts.yml`. Inside a git repo wit
|
|
|
76
76
|
|---|---|
|
|
77
77
|
| `auth` | `login` `logout` `status` `token` `refresh` |
|
|
78
78
|
| `pr` | `list` `view` `create` `merge` `approve` `unapprove` `diff` `checkout` `edit` `decline` `ready` `request-review` `comment` |
|
|
79
|
-
| `repo` | `list` `view` `create` `delete` `clone` `set-default` |
|
|
79
|
+
| `repo` | `list` `view` `create` `delete` `clone` `set-default` `rename` `fork` _(Cloud)_ |
|
|
80
80
|
| `branch` | `list` `create` `delete` `checkout` |
|
|
81
81
|
| `tag` | `list` `create` `delete` |
|
|
82
82
|
| `webhook` | `list` `view` `create` `delete` |
|
|
83
83
|
| `commit` | `log` `view` |
|
|
84
84
|
| `pipeline` | `list` `view` `run` _(Cloud only)_ |
|
|
85
|
+
| `workspace` | `list` _(Cloud only)_ |
|
|
86
|
+
| `project` | `list WORKSPACE` _(Cloud only)_ |
|
|
87
|
+
| `issue` | `list` `view` `create` `close` _(Cloud only)_ |
|
|
85
88
|
| `api` | Raw REST passthrough with pagination, `--jq`, variable expansion |
|
|
86
89
|
| `alias` | Custom command shortcuts |
|
|
87
90
|
| `config` | Editor, pager, git protocol per-host |
|
|
@@ -127,6 +130,24 @@ bitbottle branch create MYPROJ/my-service feature/x --start-at main
|
|
|
127
130
|
bitbottle branch delete MYPROJ/my-service feature/x
|
|
128
131
|
```
|
|
129
132
|
|
|
133
|
+
#### Branch protection _(Bitbucket Server / DC only)_
|
|
134
|
+
|
|
135
|
+
Branch restrictions on Bitbucket Server / DC. Cloud has a different model
|
|
136
|
+
that isn't wired up yet — invocations against Cloud return a typed
|
|
137
|
+
"unsupported on host" error.
|
|
138
|
+
|
|
139
|
+
```bash
|
|
140
|
+
bitbottle branch protect list MYPROJ/my-service
|
|
141
|
+
bitbottle branch protect create MYPROJ/my-service \
|
|
142
|
+
--type fast-forward-only --branch main \
|
|
143
|
+
--user alice --group devs
|
|
144
|
+
bitbottle branch protect delete MYPROJ/my-service 42
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
`--type` accepts `read-only`, `no-deletes`, `fast-forward-only`, or
|
|
148
|
+
`pull-request-only`. Pass exactly one of `--branch NAME` (literal branch)
|
|
149
|
+
or `--pattern GLOB` (e.g. `release/*`).
|
|
150
|
+
|
|
130
151
|
### Pipelines _(Cloud only)_
|
|
131
152
|
|
|
132
153
|
```bash
|
|
@@ -179,6 +200,38 @@ Event keys differ between backends:
|
|
|
179
200
|
from a file. Trailing newlines from stdin / file are trimmed. Webhook
|
|
180
201
|
secrets are write-only — neither backend returns them on read.
|
|
181
202
|
|
|
203
|
+
### Repo extras
|
|
204
|
+
|
|
205
|
+
```bash
|
|
206
|
+
# Rename (both backends — slug derives from new name on Cloud).
|
|
207
|
+
# --confirm is required on non-TTY because the slug change breaks existing
|
|
208
|
+
# clones' origin URL — run `git remote set-url origin ...` after.
|
|
209
|
+
bitbottle repo rename MYPROJ/my-service my-service-v2 --confirm
|
|
210
|
+
|
|
211
|
+
# Fork into another workspace (Bitbucket Cloud only)
|
|
212
|
+
bitbottle repo fork myworkspace/my-service --into otherws
|
|
213
|
+
bitbottle repo fork myworkspace/my-service --into otherws --name my-fork
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
`repo fork` returns a typed unsupported-capability error on Bitbucket Server /
|
|
217
|
+
Data Center, which has no fork primitive in its REST API. Both `rename` and
|
|
218
|
+
`fork` accept `--json fields` and `--jq expr` for structured output.
|
|
219
|
+
|
|
220
|
+
### Workspaces & Projects (Cloud only)
|
|
221
|
+
|
|
222
|
+
```bash
|
|
223
|
+
# Workspaces the authenticated user belongs to
|
|
224
|
+
bitbottle workspace list
|
|
225
|
+
bitbottle workspace list --json slug,name --jq '.[].slug'
|
|
226
|
+
|
|
227
|
+
# Projects within a workspace
|
|
228
|
+
bitbottle project list myworkspace
|
|
229
|
+
bitbottle project list myworkspace --limit 100
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
Both commands surface a typed unsupported-capability error against
|
|
233
|
+
Bitbucket Server / Data Center hosts (workspaces are a Cloud concept).
|
|
234
|
+
|
|
182
235
|
### Raw API
|
|
183
236
|
|
|
184
237
|
```bash
|
|
@@ -268,6 +321,20 @@ bitbottle completion --shell powershell >> $PROFILE
|
|
|
268
321
|
|
|
269
322
|
Full list in [`internal/envvars/envvars.go`](internal/envvars/envvars.go).
|
|
270
323
|
|
|
324
|
+
## Colour & pager
|
|
325
|
+
|
|
326
|
+
State columns in TTY tables are colourised: `OPEN` / `SUCCESSFUL` /
|
|
327
|
+
active webhooks render green; `MERGED` magenta; `DECLINED` /
|
|
328
|
+
`SUPERSEDED` / `FAILED` / `ERROR` / `STOPPED` / inactive webhooks red;
|
|
329
|
+
`IN_PROGRESS` / `PENDING` yellow. Colour applies to TTY table output
|
|
330
|
+
only — JSON (`--json`) and piped output stay raw.
|
|
331
|
+
|
|
332
|
+
Disable colour with the global `--no-color` flag or by setting
|
|
333
|
+
`NO_COLOR=1` in the environment. JSON output is never colourised.
|
|
334
|
+
|
|
335
|
+
Long-output commands (`pr diff`, `commit log`) pipe through `$PAGER`
|
|
336
|
+
when stdout is a TTY (default `less -FRX`). Set `PAGER=cat` to disable.
|
|
337
|
+
|
|
271
338
|
---
|
|
272
339
|
|
|
273
340
|
## Contributing
|