duoqi-api/docs/agents/issue-tracker.md
Wang Zhuoxuan 4e7a9e6d1f
Some checks failed
CI/CD Pipeline / Code Quality (push) Successful in 24s
CI/CD Pipeline / Unit Tests (push) Failing after 20s
CI/CD Pipeline / Build & Deploy Test (push) Has been skipped
CI/CD Pipeline / Build & Deploy Production (push) Has been skipped
docs: 添加 agents 配置文档
2026-05-27 22:53:14 +08:00

24 lines
1.1 KiB
Markdown

# Issue tracker: Gitea
Issues and PRDs for this repo live as Gitea issues on git.duoqi.me. Use the [`tea`](https://gitea.com/gitea/tea) CLI for all operations.
## Conventions
- **Create an issue**: `tea issues create --title "..." --description "..."`. Use a heredoc for multi-line descriptions.
- **Read an issue**: `tea issues view <number>`. Use `--output json` for machine-readable output.
- **List issues**: `tea issues list --output json` with appropriate `--labels` filters.
- **Comment on an issue**: `tea issues add-comment <number> --message "..."`.
- **Apply / remove labels**: `tea issues edit <number> --labels "..."`.
- **Close**: `tea issues close <number>`. Post the explanation first with `tea issues add-comment <number> --message "..."`, then close.
- **Pull requests**: Use `tea pr create`, `tea pr view`, `tea pr add-comment`, etc. — similar shape to `gh pr ...`.
Infer the repo from `git remote -v``tea` does this automatically when run inside a clone.
## When a skill says "publish to the issue tracker"
Create a Gitea issue.
## When a skill says "fetch the relevant ticket"
Run `tea issues view <number>`.