@sjawhar/pi-legion 18.52.1 → 18.52.2
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
|
@@ -14337,7 +14337,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
|
|
|
14337
14337
|
// package.json
|
|
14338
14338
|
var package_default = {
|
|
14339
14339
|
name: "@sjawhar/pi-legion",
|
|
14340
|
-
version: "18.52.
|
|
14340
|
+
version: "18.52.2",
|
|
14341
14341
|
license: "Apache-2.0",
|
|
14342
14342
|
type: "module",
|
|
14343
14343
|
omp: {
|
|
@@ -36,6 +36,7 @@ Read each by its `skill://` link: a read by path stops at 300 lines.
|
|
|
36
36
|
|
|
37
37
|
| When | Read |
|
|
38
38
|
| --- | --- |
|
|
39
|
+
| Before the turn's first `jj new` or commit, in a workspace you share | `skill://legion-worker/references/foreign-path.md` |
|
|
39
40
|
| You write or edit the PR body, record a result against a check, read another phase's results, or run the simplify pass | `skill://legion-worker/references/pr-body.md` |
|
|
40
41
|
| Before a push, to check your commits' App identity | `skill://legion-worker/references/default-branch-check.md` |
|
|
41
42
|
| You reply on, list or resolve review threads, or judge a bot's finding | `skill://legion-worker/references/review-threads.md` |
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# A path you did not write
|
|
2
|
+
|
|
3
|
+
Your workspace is shared with the issue's other roles. Read this before the `jj new` your
|
|
4
|
+
role prompt has you run at the turn's start, and so before your first commit:
|
|
5
|
+
|
|
6
|
+
cd -- "$LEGION_WORKSPACE" && jj -R "$LEGION_WORKSPACE" diff -r @ --name-only
|
|
7
|
+
jj -R "$LEGION_WORKSPACE" diff --from "legion/<issue>@origin" --to @ --name-only
|
|
8
|
+
|
|
9
|
+
(Read the second against your default branch at origin before this branch's first push.)
|
|
10
|
+
Every path yours: commit and push as your role prompt says. A path you did not write that is
|
|
11
|
+
only in the second list, or already inside a commit of yours: split nothing, tell the architect.
|
|
12
|
+
A path you did not write in the first list:
|
|
13
|
+
|
|
14
|
+
cd -- "$LEGION_WORKSPACE" && jj -R "$LEGION_WORKSPACE" split -m '<issue>: <what you did>' <your paths…>
|
|
15
|
+
jj -R "$LEGION_WORKSPACE" metaedit -r @- --update-author
|
|
16
|
+
jj -R "$LEGION_WORKSPACE" bookmark set legion/<issue> -r @-
|
|
17
|
+
jj -R "$LEGION_WORKSPACE" git push --bookmark legion/<issue>
|
|
18
|
+
|
|
19
|
+
No `jj new` first: the push carries that path unless its parent has no description. This split is
|
|
20
|
+
the one exception to "Never `jj describe` or `jj split` the working-copy commit you found at the
|
|
21
|
+
turn's start", and the metaedit is why. Always `-m`, or your commit has no message of yours.
|
|
22
|
+
The remainder keeps that path, and the push above moves the bookmark's commit alone, so it stays
|
|
23
|
+
out of the branch. Never put the bookmark on the remainder, described or not: measured, that
|
|
24
|
+
pushes the other role's file. Read the first list again, then tell the architect what it held.
|
|
25
|
+
Recover forward (`jj new`, `jj restore <paths>`), never `jj undo`, `jj abandon` or `jj op restore`.
|