@staff0rd/assist 0.683.0 → 0.684.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 +3 -2
- package/allowed.cli-reads +1 -0
- package/dist/allowed.cli-reads +1 -0
- package/dist/commands/sessions/web/bundle.js +1 -1
- package/dist/index.js +359 -226
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -160,6 +160,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
|
|
|
160
160
|
- `assist github issue fix-structure <target> [-R <owner>/<repo>] [--level <level>] [--type-chain <names>] [--strip-label <label>...] [--apply]` - Normalise the issue types across one issue subtree, reading and writing nothing outside it. `<target>` is `owner/repo#number`, a github.com issue URL, or a bare number with `-R`; a bare number with no repo is refused rather than guessed. Walks the subtree via sub-issues level by level (a single deep query blows the GraphQL node limit) and reports the type each issue should carry: every level below the target is typed to the next level down the chain, matching type names loosely so `Subtask` and `Sub-task` both bind to the leaf. The chain defaults to `Epic` > `Story` > `Subtask`; `--type-chain Initiative,Feature,Task` replaces it, parent level first, and every level named must already exist as an issue type on the organisation or the run fails listing the ones that do. Untyped issues are typed rather than skipped, and cross-repo children are handled in the one run. The target's own level is inferred from its issue type, so aiming at a story types its children as subtasks; when its type is not in the chain the level cannot be inferred and the command exits non-zero naming the type it has. `--level` asserts the position instead, which also types the target itself. No label is touched unless `--strip-label` names it; it is repeatable, matched case-insensitively, and each label is removed by the id found on that issue, since label ids differ per repository. Anything nested below the leaf level fails the run before a single write, naming the offender and its parent; nothing is ever re-parented. Without `--apply` nothing is written. `--apply` announces each write before it is issued and flushes it, so a long run shows progress, then re-walks the subtree and fails with a non-zero exit if any drift remains
|
|
161
161
|
- `assist news add [url]` - Add an RSS feed URL (rendered in the sessions web News tab)
|
|
162
162
|
- `assist releases [list]` - Print the declared release promotion streams — each stream's repo, release workflow, nodes and edges — as read from `releases.streams`. The same declaration drives the [Releases page](#releases) of the sessions dashboard
|
|
163
|
+
- `assist releases configure <owner/repo>` - Derive that repo's promotion topology and write it to `releases.streams`. Launches a Claude session that reads the repo's workflow files from GitHub, follows every `uses:` reusable-workflow call to whatever depth it nests, flattens the `needs:` graph across those boundaries into nodes and edges, and confirms the graph with you before writing. On exit the command re-reads the config: a block that fails the schema is reported field by field and exits non-zero, and a valid one is printed back as the environments, steps and edges it derived for that repo. Streams declared for other repos are left alone
|
|
163
164
|
|
|
164
165
|
### Backlog
|
|
165
166
|
|
|
@@ -452,7 +453,7 @@ releases:
|
|
|
452
453
|
```
|
|
453
454
|
|
|
454
455
|
- `id` names the node within the stream and is what `edges` refer to. A node with an `environment` is a GitHub deployment environment and reads live state; `kind` (`build` or `gate`) marks a node that deploys nothing. `label` overrides the text on the node, which is otherwise the `id`.
|
|
455
|
-
- `assist releases
|
|
456
|
+
- `assist releases configure <owner/repo>` derives the block for a repo instead of hand-writing it, and `assist releases list` prints whatever is declared back as assist reads it.
|
|
456
457
|
|
|
457
458
|
## Parallel work
|
|
458
459
|
|
|
@@ -488,7 +489,7 @@ A restart kills every managed session's pty, which also kills any background tas
|
|
|
488
489
|
- `commit.expectedBranch` — when set (e.g. `main`), `assist commit` prints a non-blocking warning if HEAD is on any other branch, so work on a stray branch isn't silently orphaned
|
|
489
490
|
- `branch.prefix` — when set (e.g. `sw`), `assist branch <slug>` prepends `<prefix>/` to the branch name
|
|
490
491
|
- `branch.defaultBranch` — override the base branch, which is otherwise resolved live from the remote (`git ls-remote --symref origin HEAD`), falling back to `main`
|
|
491
|
-
- `releases.streams` — the release promotion streams drawn by the [Releases page](#releases) and printed by `assist releases list`
|
|
492
|
+
- `releases.streams` — the release promotion streams drawn by the [Releases page](#releases), derived by `assist releases configure <owner/repo>` and printed by `assist releases list`
|
|
492
493
|
- `cliHook.blockNpmRun` — when `true` (default), `assist cli-hook` denies `npm run` and redirects to `assist run <name>`, `assist verify` or `assist build`. Set it to `false` in a repo that genuinely needs npm scripts. `npm install`, `npm ci` and `npm test` are never affected
|
|
493
494
|
|
|
494
495
|
## Acceptance criteria outliner extension
|
package/allowed.cli-reads
CHANGED