You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/docs/src/content/docs/extend/github-plugin.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,8 @@ When `GITHUB_WEBHOOK_SECRET` is configured, GitHub tools can return subscribable
135
135
pull request and issue resources. Junior can use those resources in two ways. A
136
136
temporary resource watch sends matching updates back to the current Slack
137
137
thread. A durable event task runs a stored instruction whenever its selected
138
-
events occur and remains active for the Slack channel until someone deletes it.
138
+
events occur and remains configured for the Slack channel until someone deletes
139
+
it.
139
140
140
141
Both forms run headlessly as Junior, not as the webhook sender. Resource watches
141
142
use the plugin's scoped installation credentials. Event tasks make their
@@ -159,7 +160,7 @@ Supported GitHub webhook deliveries become these Junior resource events:
159
160
`pull_request.merged` and `pull_request.closed_unmerged` complete a temporary
160
161
pull request watch after Junior accepts the event. Other watch events remain
161
162
active until the watch expires or is cancelled. Event tasks do not complete
162
-
after a terminal event; they remain active until deleted.
163
+
after a terminal event; they remain configured until deleted.
163
164
164
165
Issue events can target one issue with `owner/repo#number` or every issue in a
165
166
repository with `owner/repo`. Webhook events use normal queued delivery. They do
@@ -271,7 +272,7 @@ expected follow-up in the original conversation.
271
272
- Deployment metadata is available but Junior never offers to watch it: `GITHUB_WEBHOOK_SECRET` is missing. Set it, redeploy, and run `github_getDeployment` again.
272
273
- GitHub webhook delivery returns `401`: the webhook secret in GitHub App settings does not match `GITHUB_WEBHOOK_SECRET`, or GitHub did not send `X-Hub-Signature-256`. Update the app webhook secret and retry the delivery.
273
274
- GitHub webhook delivery returns `202 Ignored`: the delivery was signed correctly but does not map to a supported deployment, pull request, or issue event. Use one of the configured event types above.
274
-
- GitHub delivery succeeds but no Slack follow-up appears: confirm the destination has an active resource watch or event task for the same identifier and event type. A successful webhook alone does not create either one.
275
+
- GitHub delivery succeeds but no Slack follow-up appears: confirm the destination has a resource watch or event task for the same identifier and event type. A successful webhook alone does not create either one.
275
276
- Missing repository context: Junior could not determine which repository to use. Include `owner/repo` directly in the GitHub request, or configure a default GitHub repository for that thread, and retry.
276
277
- A `403` response that says to use `github_createIssue` or `github_createPullRequest` is a Junior routing denial, not evidence of missing App permissions. Retry with the named tool.
277
278
- Private OAuth prompt for a human-identity operation such as a pull request review: the actor has not authorized the GitHub App yet, or the stored user-to-server token expired. Complete the private authorization prompt; do not paste personal access tokens into the chat or sandbox.
Copy file name to clipboardExpand all lines: packages/junior/src/chat/tools/create-event-task.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ export function createEventTaskTool(
36
36
},
37
37
executionMode: "sequential",
38
38
description:
39
-
"Create a durable event task that executes the supplied instruction for every matching resource event. Use for whenever-this-happens-do-X automation; ordinary watch, notify, or tell-me-when requests use watchResourceEvents instead. The task remains active for this Slack channel or DM until deleted and may use the creator's connected credentials. Prefer a subscribable tool result when available.",
39
+
"Create a durable event task that executes the supplied instruction for every matching resource event. Use for whenever-this-happens-do-X automation; ordinary watch, notify, or tell-me-when requests use watchResourceEvents instead. The task remains configured for this Slack channel or DM until deleted and may use the creator's connected credentials. Prefer a subscribable tool result when available.",
0 commit comments