GitHub

Inbound hooks return { auth } to dispatch, or null to ignore. Use defaultGitHubAuth(ctx) to derive auth from the actor.

import { defaultGitHubAuth, githubChannel } from "eve/channels/github";

export default githubChannel({
  botName: "my-agent",
  // Replaces the @mention gate. ctx.conversation.kind is "issue", "pull_request", or "review_thread".
  onComment: (ctx, comment) => ({ auth: defaultGitHubAuth(ctx) }),
  // Opt in; no default dispatch on these events.
  onIssue: (ctx, issue) => (issue.action === "opened" ? { auth: defaultGitHubAuth(ctx) } : null),
  onPullRequest: (ctx, pr) => (pr.action === "opened" ? { auth: defaultGitHubAuth(ctx) } : null),
  onCheckSuite: (ctx, suite) =>
    suite.action === "completed" &&
    suite.conclusion === "failure" &&
    suite.app.slug === "github-actions" &&
    suite.pullRequests.length > 0
      ? {
          auth: defaultGitHubAuth(ctx),
          context: [`Triage failed check suite ${suite.checkSuiteId} at ${suite.headSha}.`],
        }
      : null,
});

The CI hooks expose normalized action, status, conclusion, app.slug, headSha, and pullRequests fields, plus checkSuiteId, checkRunId, or workflowRunId. workflow_run is a GitHub Actions-only event, so its normalized app.slug is "github-actions". A dispatched CI turn is anchored to the first number in pullRequests; the hook still runs when the array is empty, but it must return null because there is no issue or PR thread for the session.

When a turn starts, the channel adds an eyes reaction to the triggering comment (turn this off with progress: { reactions: false }). The reply comes back as a comment, on the timeline or in the review thread, and splits across multiple comments when it runs long. If the turn fails, you get a short error comment carrying an error id.

GitHub comments have no interactive button or card affordance. A human-in-the-loop (HITL) input.requested event is posted as a comment prompt, and the user's reply comment maps back to the pending input request. Declare an events["input.requested"] handler to customize the prompt.

Start a session without an inbound mention through receive(github, { message, target, auth }) from a schedule run handler, or args.receive(github, ...) from another channel. The target requires owner, repo, and exactly one of issueNumber or pullRequestNumber.

Inbound file attachments are not supported on this channel today. Repository contents reach the agent through the sandbox checkout below, not as message attachments.

Summon the agent on a PR and it always sees the diff. PR metadata and the changed-file patch land in context. Large generated files still appear in the list, but their patch body is dropped; add more paths to the skip list with pullRequestContext.excludedFiles.