GitHub
Connect repositories and configure the handler for GitHub mentions.
The Ellipsis GitHub App gives sessions access to your repositories and answers @ellipsis on issues and pull requests.
Answer a mention
- Install the Ellipsis GitHub App and choose the repositories it can access.
- Comment
@ellipsiswith a question on an issue or pull request in one of them.
Change the repository list later in GitHub's settings for installed apps.
Repository access
The environment chooses which repositories a session checks out. Session permissions can further limit its GitHub token.
- Environment schema reference configures checkouts
- Permissions controls reads and writes
- Triggers starts agents from repository events
Mentions
Mention @ellipsis on an issue or pull request to start or continue a session. Without a github.yaml, the built-in handler answers.
To customize the handler, put github.yaml at the root of your organization's .ellipsis repository:
Mentions in api-repo and web-repo use this handler; other repositories use the built-in one. Set github.repositories: ['*'] to use it everywhere; don't combine '*' with names.
The session block works like an agent's. The default-branch version is live, and an invalid edit keeps the last valid one. Set ellipsis.enabled: false to go back to the built-in handler. Only the copy in the .ellipsis repository counts.
Who can mention Ellipsis
github.mentions controls which authors can summon Ellipsis and whether a comment starting with ... or … counts as a mention:
People can summon Ellipsis in public and private repositories; bots such as Dependabot and Renovate can't. A comment starting with ... or … also counts.
These settings apply in every repository, including ones your handler doesn't cover and while it's disabled. Omitted fields use the defaults above, even without a github.yaml. The dashboard shows the settings in effect.