@sjawhar/pi-legion 19.31.3 → 19.31.4
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/dist/legion.js
CHANGED
|
@@ -29803,7 +29803,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
|
|
|
29803
29803
|
// package.json
|
|
29804
29804
|
var package_default = {
|
|
29805
29805
|
name: "@sjawhar/pi-legion",
|
|
29806
|
-
version: "19.31.
|
|
29806
|
+
version: "19.31.4",
|
|
29807
29807
|
license: "Apache-2.0",
|
|
29808
29808
|
type: "module",
|
|
29809
29809
|
omp: {
|
|
@@ -119,8 +119,12 @@ architect for it, whatever it asks. For a person's mention, take the first of th
|
|
|
119
119
|
says, so `admission.active` names some of a tree's waits as well as its work. Say what you
|
|
120
120
|
read, citing for each fact the `read_state` field or the `dispatch read` line it came from.
|
|
121
121
|
- **A request for work.** Someone wants a change made, a bug fixed, something investigated. Search
|
|
122
|
-
first (`skill://dispatch-first`)
|
|
123
|
-
|
|
122
|
+
first (`skill://dispatch-first`).
|
|
123
|
+
When the open issue that tracks it is one Legion runs, the request is that tree's work: pass it
|
|
124
|
+
to its architect as **Something an issue's architect owns** below says, since a reply naming the
|
|
125
|
+
issue reaches nobody.
|
|
126
|
+
When the issue that tracks it is nobody's tree, reply with that issue and file nothing.
|
|
127
|
+
Otherwise file one issue in the project:
|
|
124
128
|
|
|
125
129
|
```text
|
|
126
130
|
dispatch issue --project <PROJECT> --title '<the request, as a title>' --spec-file - <<'EOF'
|