launchpad/docs/agents/issue-tracker.md

Issue tracker: Gitea

Issues for this repo live in Gitea at git.forteapps.net/Forte/launchpad. Use the Gitea API or tea CLI.

Conventions

• Create an issue: tea issue create --title "..." --description "..." or via API: curl -X POST "https://git.forteapps.net/api/v1/repos/Forte/launchpad/issues" -H "Authorization: token $GITEA_TOKEN" -H "Content-Type: application/json" -d '{"title":"...","body":"..."}'
• Read an issue: tea issue view <number> or API GET /api/v1/repos/Forte/launchpad/issues/<number>
• List issues: tea issue list or API GET /api/v1/repos/Forte/launchpad/issues?state=open
• Comment on an issue: tea issue comment <number> "..." or API POST /api/v1/repos/Forte/launchpad/issues/<number>/comments
• Apply labels: API POST /api/v1/repos/Forte/launchpad/issues/<number>/labels with {"labels": [<label_id>]}
• Close: API PATCH /api/v1/repos/Forte/launchpad/issues/<number> with {"state": "closed"}

Infer the repo from git remote -v.

Pull requests as a triage surface

PRs as a request surface: no.

When a skill says "publish to the issue tracker"

Create a Gitea issue.

When a skill says "fetch the relevant ticket"

Fetch the issue via API or tea issue view <number>.