forked from bkinnightskytw/code_work_spawner
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
# Config Examples
|
|
|
|
The repo uses an Agent Orchestrator style YAML config with `defaults` and `projects`.
|
|
|
|
Project entries can override `issueAssistant` fields when a repo needs a
|
|
different prompt, mention triggers, responder chain, or notification list.
|
|
|
|
Generated comments include both a visible prefix and footer by default so it is
|
|
clear the reply came from automation even when `gh` is authenticated as a human
|
|
account. Those markers support template variables such as `{{gh_login}}`,
|
|
`{{repo}}`, `{{project_key}}`, `{{issue_number}}`, `{{trigger}}`,
|
|
`{{comment_tag}}`, and `{{fingerprint}}`. Set either template to an empty
|
|
string to disable that section.
|
|
|
|
Discord notifications are configured under `issueAssistant.notifications`.
|
|
Currently supported fields are:
|
|
|
|
- `type: discordWebhook`
|
|
- `enabled`
|
|
- `events`: any of `mention_detected`, `reply_posted`, `no_reply`, `responder_failed`
|
|
- `webhookUrl`
|
|
- `username`
|
|
- `avatarUrl`
|
|
|
|
Start from [`examples/simple-github.yaml`](simple-github.yaml). This
|
|
repo uses `dataDir`, `worktreeDir`, and `projects`, and uses `worktreeDir` for
|
|
bug-verification worktrees.
|