@sjawhar/pi-envoy 10.12.0 → 10.14.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/dist/dispatch.js +10 -0
- package/dist/envoy.js +10 -0
- package/dist/skills/dispatch/references/asks.md +1 -1
- package/package.json +1 -1
package/dist/dispatch.js
CHANGED
|
@@ -13566,6 +13566,16 @@ var ASK_TURNS = ["human", "agent"];
|
|
|
13566
13566
|
var DELIVERY_CAPABILITIES = ["aside", "btw", "steer"];
|
|
13567
13567
|
var DELIVERY_DUPLICATE_WINDOW_MS = 72 * 60 * 60 * 1000;
|
|
13568
13568
|
var SEARCH_DEGRADED_EMBEDDER_UNAVAILABLE = "embedder_unavailable";
|
|
13569
|
+
var IssueDeployedEventPayloadSchema = exports_external.strictObject({
|
|
13570
|
+
repo: exports_external.string(),
|
|
13571
|
+
number: exports_external.number().int().positive(),
|
|
13572
|
+
run_id: exports_external.number().int().positive(),
|
|
13573
|
+
completed_at: exports_external.iso.datetime()
|
|
13574
|
+
});
|
|
13575
|
+
var DispatchServerStartedPayloadSchema = exports_external.strictObject({
|
|
13576
|
+
commit: exports_external.string().min(1),
|
|
13577
|
+
started_at: exports_external.iso.datetime()
|
|
13578
|
+
});
|
|
13569
13579
|
var DispatchEventSchema = exports_external.object({
|
|
13570
13580
|
issue_key: exports_external.string().nullable(),
|
|
13571
13581
|
artifact_id: exports_external.string().nullish(),
|
package/dist/envoy.js
CHANGED
|
@@ -29655,6 +29655,16 @@ var DEFAULT_ISSUE_PAGE_LIMIT = 50;
|
|
|
29655
29655
|
var ASK_TURNS = ["human", "agent"];
|
|
29656
29656
|
var DELIVERY_CAPABILITIES = ["aside", "btw", "steer"];
|
|
29657
29657
|
var DELIVERY_DUPLICATE_WINDOW_MS = 72 * 60 * 60 * 1000;
|
|
29658
|
+
var IssueDeployedEventPayloadSchema = exports_external.strictObject({
|
|
29659
|
+
repo: exports_external.string(),
|
|
29660
|
+
number: exports_external.number().int().positive(),
|
|
29661
|
+
run_id: exports_external.number().int().positive(),
|
|
29662
|
+
completed_at: exports_external.iso.datetime()
|
|
29663
|
+
});
|
|
29664
|
+
var DispatchServerStartedPayloadSchema = exports_external.strictObject({
|
|
29665
|
+
commit: exports_external.string().min(1),
|
|
29666
|
+
started_at: exports_external.iso.datetime()
|
|
29667
|
+
});
|
|
29658
29668
|
var DispatchEventSchema = exports_external.object({
|
|
29659
29669
|
issue_key: exports_external.string().nullable(),
|
|
29660
29670
|
artifact_id: exports_external.string().nullish(),
|
|
@@ -7,7 +7,7 @@ thread. Whether to ask at all, and how to write the question, is "Before you ask
|
|
|
7
7
|
|
|
8
8
|
## Who answers an ask
|
|
9
9
|
|
|
10
|
-
An ask goes to the issue's assignee: their Inbox opens on
|
|
10
|
+
An ask goes to the issue's assignee: their Inbox opens on the asks on the issues they hold, so a question on an issue someone is assigned is in front of that person. An ask on an issue nobody is assigned is in nobody's default Inbox list and in nobody's `Needs you` count; it is reached by adding `Unassigned` to the Inbox's assignee filter, or from the issue's own page. Setting the issue's assignee is what puts a question in front of a person. Find out who Dispatch takes you for with `dispatch whoami`.
|
|
11
11
|
It prints whom the session acts for: the lowercase email of the person whose personal token you run under, or, under the shared token or a verified service token, that it has no owner — naming the service as `<namespace>/<name>` for a service token (`system:serviceaccount:<namespace>:<name>`), which is also how every write you make is rendered (`(as <namespace>/<name>)`) — the namespace is kept because every namespace has a `default` service account, and a subject that is not a Kubernetes one is shown whole. An issue you create without `--assignee` goes to your owner; with no owner it inherits its parent's assignee, or stays unassigned without a parent. If an issue you are asking on is unassigned and the answer matters, assign it to your owner (`PATCH /api/v1/issues/{key}` with `{"assignee": "<email>"}`; any authenticated caller may reassign, and an email nobody has signed in with is refused with `ASSIGNEE_NOT_ALLOWED`) or name in the question who should answer it. Never reassign an issue a human holds to get an answer faster: that is the human's call.
|
|
12
12
|
|
|
13
13
|
## Handing a human a to-do, editing, resolving, and replying
|