code_work_spawner/examples
insleker cf1d8ec782 feat: add Gitea issue tracker support (#6)
Support projects hosted on Gitea via tea so the poller can fetch issues, read threads, and post replies across both supported trackers.
2026-04-06 09:22:30 +08:00
..
README.md feat: add Gitea issue tracker support (#6) 2026-04-06 09:22:30 +08:00
simple-gitea.yaml feat: add Gitea issue tracker support (#6) 2026-04-06 09:22:30 +08:00
simple-github.yaml feat: add Gitea issue tracker support (#6) 2026-04-06 09:22:30 +08:00

README.md

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 or tea is authenticated
as a human account. Those markers support template variables such as
{{tracker_login}}, {{tracker_cli}}, {{repo}}, {{project_key}},
{{issue_number}}, {{trigger}}, {{comment_tag}}, and {{fingerprint}}.
{{gh_login}} is still populated for backward compatibility. 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 for GitHub or
examples/simple-gitea.yaml for Gitea. This repo uses
dataDir, worktreeDir, and projects, and uses worktreeDir for
bug-verification worktrees.