@staff0rd/assist 0.735.0 → 0.737.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
@@ -510,9 +510,13 @@ releases:
510
510
 
511
511
  ## Next
512
512
 
513
- The **Next** tab (`/next`) answers "what should I do next?" from the selected repo, across the GitHub repos that repo is configured to span. `next.repos` lists the repos it reads, defaulting to the selected repo: an `owner/name` entry reads that repo, and a bare `owner` (an org or user) reads every unarchived repo it owns through GitHub search; set it per repo with `-g --repo` so each repo's Next view spans its own set. Across those repos it lists open PRs, skipping drafts and do-not-merge titles (`[DNM]`, `[Do Not Merge]`) as `prs status` does, authored by a login in `next.peers` or requesting your review, hiding peer PRs you approved at their current head commit, ordered by your latest review request (or creation, for an unrequested peer PR), oldest first. Below them come open issues assigned to you, oldest first, then unassigned open issues on the GitHub Projects in `next.projects` (`owner/number` entries, items from any repo) whose Status is in `next.pickStatuses` (default `Ready`, `Todo`), skipping any carrying a label in `next.excludeLabels` or whose GitHub issue type is in `next.excludeTypes` (both case-insensitive). Pickups from every project form one list, ranked by each item's position in its own project's Priority options (unset last), then oldest first. Reading a project needs the gh `project` scope; a project that cannot be read shows its error in the pickup section while the other projects' items still show. The header shows the current peers, repos and projects, with the command for any that is unset.
513
+ The **Next** tab (`/next`) recommends what to do next, in this order:
514
514
 
515
- The top item (peer PRs, then issues, then pickups) is shown as a hero with a line explaining why it was chosen, and every item shows its `owner/name#number`. Every item has **Start session** and **GitHub**. Start session runs in the local clone of the item's repo (matched by origin among the repos the web app knows), and is disabled when there is none: on a PR it opens the same review type dialog as the toolbar `prs` dropdown; on an issue it opens the new-session dialog prefilled with the issue reference; on a pickup it first assigns the issue to you and moves its project item to In Progress (`POST /api/next/pickup`), then opens the same dialog. Opening `/?new=<text>&newCwd=<path>` prefills the new-session prompt and repo the same way. A source that fails to load, or one of its repos that cannot be read, shows its error in its own section without hiding the rest. Data comes from `GET /api/next?cwd=<repo>`, with gh results cached for 30s.
515
+ 1. **Peer PRs** — open PRs across `next.repos` by `next.peers` or requesting your review
516
+ 2. **Assigned issues** — open issues assigned to you across `next.repos`
517
+ 3. **Pickups** — unassigned items on `next.projects` boards in a `next.pickStatuses` status, in board order
518
+
519
+ **Start session** runs in the item's local clone: PRs open the review dialog, issues open the new-session dialog, and pickups are assigned to you and moved to In Progress first. Project pickups need the gh `project` scope. See `assist sessions web --help` for each key.
516
520
 
517
521
  ```bash
518
522
  assist config set next.peers alice,bob -g --repo