@staff0rd/assist 0.732.1 → 0.733.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,13 +510,15 @@ 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. The header shows the current peers and repos, with the command for any that is unset.
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 Project in `next.project` (`owner/number`, from any repo) whose Status is in `next.pickStatuses` (default `Ready`, `Todo`), highest priority first by the order of the project's Priority options. Reading the project needs the gh `project` scope; without it the pickup section says so. The header shows the current peers, repos and project, with the command for any that is unset.
514
514
 
515
- The top item (peer PRs before issues) 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. 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
+ 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.
516
516
 
517
517
  ```bash
518
518
  assist config set next.peers alice,bob -g --repo
519
519
  assist config set next.repos my-org,other/web -g --repo
520
+ assist config set next.project my-org/3 -g --repo
521
+ assist config set next.pickStatuses Ready,Todo -g --repo
520
522
  ```
521
523
 
522
524
  ## Parallel work