atlass 1.10.0 → 1.12.0

package/README.md

@@ -30,8 +30,9 @@ atlass auth logout
 Site and email go in `~/.config/atlass/config.json`. The token goes in the OS
 keyring. One account at a time.
 
-Bitbucket needs its own Bitbucket-scoped token with pipeline and workspace read
-scopes, since Atlassian tokens are scoped per product:
+Bitbucket needs its own Bitbucket-scoped token with pipeline, pull request,
+account, and workspace read scopes, since Atlassian tokens are scoped per
+product:
 
 ```bash
 atlass bitbucket login    # prompts for workspace, default repo, and token
@@ -97,6 +98,31 @@ body sent is everything between the H1 and `## Comments`.
 - Confluence uploads local images referenced in the body as attachments. Jira
   update does not support image changes yet.
 
+## Create
+
+```bash
+atlass jira create                              # prompts for everything
+atlass jira create BSC Bug --summary "Login loops" --priority High --label auth
+atlass jira create BSC Task -s "Rotate keys" --description-file notes.md --assignee me
+atlass jira create BSC Defect -s "..." --component API --field severity=S2 --dry-run
+atlass jira fields BSC                          # issue types you can create
+atlass jira fields BSC Defect                   # the create form for one type
+```
+
+With no field flags on a terminal, `create` walks through the create screen:
+required fields, a pick list of optional ones, then a review and confirm.
+Multi-line fields open `$EDITOR` for Markdown.
+
+Any field flag, `--no-input`, or a non-terminal switches to strict mode:
+nothing is prompted, and the command fails before creating anything if a
+required field is missing, a value is not allowed, or a field is not on the
+create screen. `--field NAME=VALUE` takes the display name or id. Multi-value
+fields take commas or repeated flags; cascading selects take `Parent > Child`;
+assignees take `me`, an account id, or a name matching one assignable user.
+
+`--dry-run` prints the resolved payload. `--json` prints the created key, id,
+and URL. `jira fields` shows what each field expects.
+
 ## List
 
 ```bash
@@ -139,7 +165,13 @@ atlass jira projects [query]
 atlass jira statuses [query] [--project PROJ]
 ```
 
-## Bitbucket pipelines
+## Bitbucket
+
+`--repo` takes `workspace/slug` or a bare slug under the configured workspace,
+and defaults to the repo set at login. `--limit` and `--json` work as for
+search.
+
+### Pipelines
 
 ```bash
 atlass bitbucket pipelines                    # recent runs for the default repo
@@ -147,8 +179,27 @@ atlass bitbucket pipelines --repo acme/web
 atlass bitbucket pipeline 124                 # one run and its steps
 ```
 
-`--repo` takes `workspace/slug` or a bare slug under the configured workspace.
-`--limit` and `--json` work as for search.
+`pipelines` shows runs as `#NUM  Status  Age  ref (commit) · duration`, newest
+first. `pipeline` adds the trigger, the creator, and the steps.
+
+### Pull requests
+
+```bash
+atlass bitbucket prs                          # open PRs on the default repo
+atlass bitbucket prs --state merged --limit 10
+atlass bitbucket prs --all                    # every state
+atlass bitbucket prs --reviewer me            # waiting on your review
+atlass bitbucket prs --author me --repo acme/web
+atlass bitbucket prs --query 'destination.branch.name = "main"'
+```
+
+`prs` shows `#ID  State  Age  Title`, most recently updated first, open only
+unless `--state` or `--all` says otherwise. Drafts show as `DRAFT` in place of
+`OPEN`.
+
+`--author` and `--reviewer` combine with OR, so passing both lists everything
+involving that person. `--query` replaces them and cannot be used alongside
+them, and it cannot mention `state`, which `--state` owns.
 
 ## Development
 

package/dist/bitbucket.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { n as buildStandalone, r as fail } from "./build-Colq1d4N.mjs";
+import { n as buildStandalone, r as fail } from "./build-2A5pjMrK.mjs";
 //#region src/bitbucket.ts
 buildStandalone("bitbucket").parseAsync().catch(fail);
 //#endregion