docs: add tea CLI workflow to CLAUDE.md for Gitea operations

2026-04-28 21:56:46 +02:00
parent ee569250ad
commit 967bacf231
1 changed files with 36 additions and 0 deletions
@@ -83,3 +83,39 @@ This is a common problem. Nextcloud aggressively caches JS assets. Escalation pa
 - Repo: `shahondin1624/Mitgliederverwaltung` on `git.shahondin1624.de`
 - Issues use labels: `enhancement`, `bug`, `backend`, `frontend`, `security`, `epic`, `priority:high/medium/low`
 - Close issues via commit message: `(Closes #N)`
+
+### Using `tea` CLI
+
+Always use the `tea` CLI for Gitea operations (never the web UI or raw API calls):
+
+```bash
+# Pull requests
+teaprclose<PR>
+teaprclose<PR>
+teapr create --head <branch> --title "<title>" --labels "<labels>" --description "<body>"
+teapr list
+teapr view <PR>
+teapr diff <PR>
+teapr merge <PR>
+
+# Issues
+tei list --state open
+tei create --title "<title>" --labels "<labels>"
+tei view <Issue>
+tei close <Issue>
+tei update <Issue> --labels "<new-labels>" --assignees "<user>"
+
+# Labels
+tel list
+tel create <name> --color "<hex>" --description "<desc>"
+
+# Milestones
+tems list
+tms create --title "<title>" --deadline "YYYY-MM-DD"
+```
+
+**Rules:**
+- Before creating a PR: ensure the branch is pushed to origin first, and verify there are actual commits on the branch (never create a PR from a branch identical to main/base)
+- Always use `tea pr diff` to verify the PR has the expected changes before merging
+- Use `tea pr merge` to merge after review
+- Close issues via commit message `(Closes #N)` — `tea` is only for PR/issue management on the Gitea server