@staff0rd/assist 0.927.0 → 0.928.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
CHANGED
|
@@ -134,7 +134,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
|
|
|
134
134
|
- `assist prs raise --title <t> --what <w> --why <y> [--how <h>] [--resolves <ref>] [--screenshot '[Group/]Caption=path']... [--force] [--draft|--no-draft]` - Raise a PR with a What/Why/How body, previewed for approval in a web session; `--draft`/`--no-draft` override `prs.draft`; each `--screenshot` is uploaded via `gh --attach` and rendered under `## Screenshots` as a `### Group` heading with a 2-column captioned table, ungrouped images last as plain images
|
|
135
135
|
- `assist prs edit [--title <t>] [--what <w>] [--why <y>] [--how <h>] [--resolves <ref>] [--screenshot '[Group/]Caption=path']...` - Update the supplied sections of the current PR's body, previewed for approval in a web session; `--screenshot` replaces the existing `## Screenshots` section
|
|
136
136
|
- `assist prs read-time <target> [--budget <duration>]` - Alias of `assist read-time`
|
|
137
|
-
- `assist prs list-comments` - List all comments on the current branch's pull request
|
|
137
|
+
- `assist prs list-comments` - List all comments on the current branch's pull request (GitHub via `gh`, or Azure DevOps via `az` when the remote is on Azure DevOps — see [Azure DevOps PRs](#azure-devops-prs))
|
|
138
138
|
- `assist prs fixed <comment-id> <sha>` - Reply with commit link and resolve thread
|
|
139
139
|
- `assist prs wontfix <comment-id> <reason>` - Reply with reason and resolve thread, previewed for approval in a web session; `-` reads the reason from stdin
|
|
140
140
|
- `assist prs reply <comment-id> <body>` - Reply to a comment thread without resolving it, previewed for approval in a web session; `-` reads the body from stdin
|
|
@@ -538,7 +538,7 @@ Concurrent sessions in one repo can be isolated with native git worktrees instea
|
|
|
538
538
|
|
|
539
539
|
- `worktree.enabled` (parallel work) — every session (prompt, assist command, backlog run, resume of a reaped worktree, `assist review` from a terminal) gets a fresh adjacent `<clone>-N` worktree; the clone itself is never allocated. Only `inPlace` launches (e.g. the PR Review button) and agents added to an existing stream stay in their tree.
|
|
540
540
|
- `worktree.trunk` (trunk-based) — a worktree's branch tracks `origin/<trunk>` so commits land on the mainline. Off, worktrees start off the remote default branch with no mainline tracking.
|
|
541
|
-
- `worktree.install` — how a new worktree installs its deps: `true` (default) auto-detects pnpm/yarn/bun/npm, a string is the install command, `false` skips it, and a list of paths installs in each in order.
|
|
541
|
+
- `worktree.install` — how a new worktree installs its deps: `true` (default) auto-detects pnpm/yarn/bun/npm (`npm ci` when a `package-lock.json` exists), a string is the install command, `false` skips it, and a list of paths installs in each in order.
|
|
542
542
|
|
|
543
543
|
None of them leaves permanent state on the clone, so turning parallel work back off leaves the repo as it was.
|
|
544
544
|
|
|
@@ -584,9 +584,11 @@ On a PR page the header button opens a menu mirroring the web app's PR dialog in
|
|
|
584
584
|
|
|
585
585
|
### Azure DevOps PRs
|
|
586
586
|
|
|
587
|
-
The content script also runs on `dev.azure.com` and `*.visualstudio.com`. On a PR page (`…/<project>/_git/<repo>/pullrequest/<id>`) it adds the **assist** button to the PR header with only **Checkout**; the review modes and
|
|
587
|
+
The content script also runs on `dev.azure.com` and `*.visualstudio.com`. On a PR page (`…/<project>/_git/<repo>/pullrequest/<id>`) it adds the **assist** button to the PR header with only **Checkout**, **Address Comments**, **Address Comments (batch)** and **Address Comments (auto)**; the review modes and Fix conflicts are GitHub-only and get a 400 for an Azure DevOps URL. The endpoint finds the clone under `clone.baseDir` whose remote is the same org/project/repo in any form (`https://org@dev.azure.com/…/_git/repo`, `https://org.visualstudio.com/…/_git/repo`, `git@ssh.dev.azure.com:v3/org/project/repo`), preferring `<baseDir>/<repo>`.
|
|
588
588
|
|
|
589
|
-
Assist stores no Azure DevOps credentials: it drives the [Azure CLI](https://aka.ms/azure-cli) with your own login, so install `az`, add its extension with `az extension add --name azure-devops`, and run `az login`. When a checkout fails, assist says which of these is missing.
|
|
589
|
+
Assist stores no Azure DevOps credentials: it drives the [Azure CLI](https://aka.ms/azure-cli) with your own login, so install `az`, add its extension with `az extension add --name azure-devops`, and run `az login`. When a checkout or an `assist prs` thread command fails, assist says which of these is missing.
|
|
590
|
+
|
|
591
|
+
In a clone whose remote is on Azure DevOps, `assist prs list-comments`, `fixed`, `wontfix` and `reply` work on the current branch's active PR through `az repos pr list` and `az devops invoke`. Each thread prints with its ADO web URL and the thread id as its `id` (every comment in a thread shares it); `fixed` replies with a `dev.azure.com/…/commit/<sha>` link and sets the thread to **Fixed**, `wontfix` sets it to **Won't fix**. A thread counts as resolved unless its status is Active or Pending.
|
|
590
592
|
|
|
591
593
|
Sending is Firefox-only (it relies on the `browser.*` promise APIs). The web server URL is set on the extension's options page (**about:addons** → the extension → **Options**) and defaults to `http://localhost:3100`. `host_permissions` covers any port on `localhost` and `127.0.0.1`; another host relies on the endpoint's CORS.
|
|
592
594
|
|
|
@@ -17,7 +17,7 @@ Comments are also cached to `~/.assist/pr-comments/{org}/{repo}/pr-{prNumber}-co
|
|
|
17
17
|
|
|
18
18
|
## Processing Comments
|
|
19
19
|
|
|
20
|
-
**Threads:** each unresolved thread block is one unit of work — never merge different threads, even when they are on the same file. Within a block, present follow-up comments (e.g., a reviewer endorsing a bot suggestion) as context alongside the primary actionable comment. Only call `fixed`/`wontfix` once per thread, using the `id` of the primary actionable comment.
|
|
20
|
+
**Threads:** each unresolved thread block is one unit of work — never merge different threads, even when they are on the same file. Within a block, present follow-up comments (e.g., a reviewer endorsing a bot suggestion) as context alongside the primary actionable comment. Only call `fixed`/`wontfix` once per thread, using the `id` of the primary actionable comment (on Azure DevOps every comment in a thread shows the thread's id).
|
|
21
21
|
|
|
22
22
|
Create a task for each unresolved **thread** (not each comment). For each thread:
|
|
23
23
|
|
|
@@ -31,7 +31,7 @@ Create a task for each unresolved **thread** (not each comment). For each thread
|
|
|
31
31
|
- Prepare a recommended fix if you believe the comment should be addressed
|
|
32
32
|
|
|
33
33
|
3. **Present options to the user** using AskUserQuestion:
|
|
34
|
-
- Include the comment URL (from `html_url` field) so the user can view it on GitHub
|
|
34
|
+
- Include the comment URL (from `html_url` field) so the user can view it on the PR's host (GitHub or Azure DevOps)
|
|
35
35
|
- **Address the comment**: Display your recommended fix and explain why it addresses the feedback
|
|
36
36
|
- **Do not address**: Display your reasoning for why the comment should not be addressed (e.g., already handled, out of scope, incorrect suggestion)
|
|
37
37
|
- **Skip**: Move on to the next comment without taking any action
|
|
@@ -46,7 +46,7 @@ Create a task for each unresolved **thread** (not each comment). For each thread
|
|
|
46
46
|
2. Run `assist prs wontfix <comment-id> "<reason>"` to reply and resolve the thread — or, if the reason contains backticks, `$(...)` or `$VAR`, use the stdin form below so your shell cannot expand it
|
|
47
47
|
- If skipping:
|
|
48
48
|
1. Do nothing — move on to the next comment immediately
|
|
49
|
-
- **Commit references**: Always use full markdown links
|
|
49
|
+
- **Commit references**: Always use full markdown links to the commit on the PR's host, never bare SHAs — `[abc1234](https://github.com/owner/repo/commit/<full-sha>)` on GitHub, `[abc1234](https://dev.azure.com/org/project/_git/repo/commit/<full-sha>)` on Azure DevOps
|
|
50
50
|
|
|
51
51
|
5. **Repeat** until all comments have been processed
|
|
52
52
|
|