GitHub

Install the Ellipsis GitHub App and select the repositories it may access. Change repository access through GitHub's installed-app settings.

Repository access

An environment selects repositories to clone. Session permissions can further restrict its GitHub token.

Environment schema reference configures checkouts
Permissions controls reads and writes
Triggers configures repository events
Code Review configures automatic reviews

Mentions

Mention @ellipsis on an issue or pull request to start or continue a conversation. With no routing file, the built-in responder handles the mention.

Put github.yaml at the root of the organization's .ellipsis repository:

ellipsis:
  version: v1
  kind: github
  name: github-helper

github:
  repositories: [api-repo, web-repo]

session:
  claude_code:
    prompt: |
      Read the relevant code before answering. When asked for a
      fix, add a regression test and run it.
  budget:
    session: 5

Mentions in api-repo and web-repo use this responder. Other repositories use the built-in responder. Set github.repositories: ["*"] to use your responder in every repository; do not combine the wildcard with repository names.

The file defines exactly one responder. ellipsis.name names it, github selects the repositories it answers in, and session holds its harness, prompt, environment, permissions, skills, and budget. An environment can be a saved environment name or an inline definition. These settings use the same structure as automation schema reference.

The default-branch version is live. Invalid edits retain the last successfully synced configuration. With ellipsis.enabled: false, mentions use the built-in responder. A copy in an ordinary repository does not configure organization mention routing.

Who can mention Ellipsis

Add github.mentions to configure which authors can summon Ellipsis and whether a leading ... or … counts as a mention:

ellipsis:
  version: v1
  kind: github
  name: github-helper

github:
  repositories: ['*']
  mentions:
    for:
      public: { users: true, bots: false }
      private: { users: true, bots: false }
    allow_leading_ellipsis: true
    require_leading_mention: false

session:
  claude_code:
    prompt: Answer questions using the relevant code.

This configuration lets people summon Ellipsis in public and private repositories, ignores bot authors such as Dependabot and Renovate, and accepts a leading ... or …. Each author and visibility combination is independent.

Field under `github.mentions`	Default	Effect
`for.public.users`	`true`	Human authors can summon Ellipsis in public repositories.
`for.private.users`	`true`	Human authors can summon Ellipsis in private repositories.
`for.public.bots`	`false`	Bot authors can summon Ellipsis in public repositories when enabled.
`for.private.bots`	`false`	Bot authors can summon Ellipsis in private repositories when enabled.
`allow_leading_ellipsis`	`true`	A comment starting with `...` or `…` can summon Ellipsis, subject to the author filters.
`require_leading_mention`	`false`	Require the mention at the start of the comment when enabled.

The mention policy applies throughout the organization, including repositories answered by the built-in responder and when ellipsis.enabled is false. The repository filter selects your custom responder; it does not limit where the mention policy applies.

Omitted fields use the defaults above. Those defaults also apply when github.mentions or the entire file is absent. Edit mention settings in github.yaml; the dashboard shows the effective policy. Invalid YAML keeps the last successfully synced policy.

Repository access

Mentions

Who can mention Ellipsis

On this page