From 8a7201b8980e6b95df4706632401d9d7fc9cdafb Mon Sep 17 00:00:00 2001 From: Steve Beaulac Date: Fri, 24 Jul 2026 00:45:32 -0400 Subject: [PATCH] docs(issue-tracker): add note that labels must be created before applying --- common/engineering/setup-skills/issue-tracker-gitea.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/engineering/setup-skills/issue-tracker-gitea.md b/common/engineering/setup-skills/issue-tracker-gitea.md index 2dde47d..d7ac0c8 100644 --- a/common/engineering/setup-skills/issue-tracker-gitea.md +++ b/common/engineering/setup-skills/issue-tracker-gitea.md @@ -8,7 +8,7 @@ Issues and PRDs for this repo live as Gitea issues. Use the `tea` CLI for all op - **Read an issue**: `tea issue --comments`. Use `-o json` for machine-readable output. - **List issues**: `tea issue list --state open -o json` with appropriate `--labels` and `--state` filters. - **Comment on an issue**: `tea comment "..."`. -- **Apply / remove labels**: `tea issue edit --add-label "..."` / `--remove-label "..."`. Multiple labels can be comma-separated or by repeating the flag. +- **Apply / remove labels**: `tea issue edit --add-label "..."` / `--remove-label "..."`. Multiple labels can be comma-separated or by repeating the flag. Labels need to be created first with `tea label create --name "..." --color "..."`. - **Close**: `tea issue close `. `tea issue close` does not accept a closing comment, so post the explanation first with `tea comment "..."`, then close. Infer the repo from git remote -v — `tea` does this automatically when run inside a clone.