@sjawhar/pi-legion 19.42.1 → 20.0.1
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
|
@@ -29931,7 +29931,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
|
|
|
29931
29931
|
// package.json
|
|
29932
29932
|
var package_default = {
|
|
29933
29933
|
name: "@sjawhar/pi-legion",
|
|
29934
|
-
version: "
|
|
29934
|
+
version: "20.0.1",
|
|
29935
29935
|
license: "Apache-2.0",
|
|
29936
29936
|
type: "module",
|
|
29937
29937
|
omp: {
|
|
@@ -22,7 +22,7 @@ says (the `held` and `worker-died` wakes, and
|
|
|
22
22
|
you set it to `todo` with a comment on the root that cites the park's mark and says what you
|
|
23
23
|
checked.
|
|
24
24
|
[The walk](#the-walk) makes that check at every start and on each `tick`.
|
|
25
|
-
Every other park, a person's, another session's or an operator's `legion status`, stays parked
|
|
25
|
+
Every other park, a person's, another session's or an operator's `legion issue status`, stays parked
|
|
26
26
|
until a person sets it to `todo`, the daemon queues a person's approval of its spec (**The
|
|
27
27
|
notice**, the paragraph that begins "A person's own approval"), or a person asks you to start it:
|
|
28
28
|
that request is a person's move, as the list of moves to `todo` in
|
|
@@ -112,10 +112,10 @@ that is not the root's primary one.
|
|
|
112
112
|
returns, so the mark's line follows the park's within the turn, and a mark older than the park
|
|
113
113
|
line belongs to an earlier park. Every other park is someone else's: a person's (`user
|
|
114
114
|
<login>`), another session's, and one by `session legion-daemon:<PROJECT>` with no mark beside
|
|
115
|
-
it. The daemon writes an operator's `legion status` and a park you made because a person
|
|
116
|
-
under that same session, so the author alone does not show your own hold. A decision older
|
|
117
|
-
the park is no reason to run: the park is the later word. When that run reaches the oldest
|
|
118
|
-
line `Events:` shows, read the root's events through the API, which keeps more than 10: the
|
|
115
|
+
it. The daemon writes an operator's `legion issue status` and a park you made because a person
|
|
116
|
+
asked under that same session, so the author alone does not show your own hold. A decision older
|
|
117
|
+
than the park is no reason to run: the park is the later word. When that run reaches the oldest
|
|
118
|
+
such line `Events:` shows, read the root's events through the API, which keeps more than 10: the
|
|
119
119
|
`curl` of [Triage a root](skill://legion-controller/references/triage.md#triage-a-root) step 2, whose
|
|
120
120
|
events carry `type`, `actor`, `created_at` and `payload.status` or `payload.body`. When the run
|
|
121
121
|
still reaches the oldest event you read, the park is that line or an older one, and you cannot
|
|
@@ -281,8 +281,8 @@ architect may have written it from issue text an outside party chose.
|
|
|
281
281
|
Four moves release a held root, at three prices. The tree's architect's own `retry_or_escalate`
|
|
282
282
|
with `retry` costs nothing. A `todo` on the root costs nothing either, and it is your own lever:
|
|
283
283
|
your `set_status` to `todo`, a person's move in the Dispatch dashboard and an operator's
|
|
284
|
-
`legion status` all reach the daemon as the same status, and each returns the issue to the
|
|
285
|
-
its hold came from and starts that phase's role with its task. Two cases end elsewhere: a held
|
|
284
|
+
`legion issue status` all reach the daemon as the same status, and each returns the issue to the
|
|
285
|
+
phase its hold came from and starts that phase's role with its task. Two cases end elsewhere: a held
|
|
286
286
|
phase whose pull request head is red goes on to `implementing`, and a held review whose round is
|
|
287
287
|
already decided goes on to the phase that decision names. Either way the daemon writes the
|
|
288
288
|
Dispatch status of the phase the issue ends in. Nothing else moves: the generation, the review
|