@sjawhar/pi-legion 19.42.0 → 19.42.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: "19.42.
|
|
29934
|
+
version: "19.42.1",
|
|
29935
29935
|
license: "Apache-2.0",
|
|
29936
29936
|
type: "module",
|
|
29937
29937
|
omp: {
|
|
@@ -70,7 +70,7 @@ Read each by its `skill://` link: a read by path stops at 300 lines.
|
|
|
70
70
|
The daemon cannot read GitHub's own `commit_id` for the review instead, because GitHub rewrites `commit_id` to the pull request's current head, so its record of a review can name a head the review never saw.
|
|
71
71
|
A review whose footer names another head, or no head, decides no round: it is set aside, the round stays open, the architect is told the reason when the review's own webhook arrived — a review only the daemon's read of GitHub's list saw leaves the architect its base reason — and the reviewer has to submit the review again at the head it read.
|
|
72
72
|
- Never write a GitHub issue, by `gh issue` or a non-GET `gh api` on `/issues` (post or edit a PR conversation comment with `gh pr comment`): Legion's issues live on Dispatch. Never run `gh config set` or `gh alias set`, and leave `GH_TOKEN`, `GITHUB_TOKEN` and `GH_HOST` empty: the daemon rewrites your gh directory in place, and a set variable outranks it.
|
|
73
|
-
- Before you report a resource unreachable, run the call through the secrets broker's client (`skill://agent-secrets`, which holds the form, the exit statuses
|
|
73
|
+
- Before you report a resource unreachable, and before you read a GitHub `404` under your own token as no access, run the call through the secrets broker's client (`skill://agent-secrets`, which holds the form, the exit statuses, where a name comes from and what a `404` means), and check `AWS_CONFIG_FILE` (read its profiles): a deployment can give your pod either. Your `task` subagents and background jobs inherit both, and your `gh` and `git`. Request a secret only to use it for your issue's work.
|
|
74
74
|
|
|
75
75
|
## Deployment instructions
|
|
76
76
|
|