ldaume Gitea Tea
Use this when Gitea state should be inspected or changed through the tea CLI
instead of the browser.
Project Fit Check
Before running commands:
- Check whether
teais installed and which login/profile is active. - Read repo remotes and local branch state before inferring owner/repo.
- Confirm destructive actions: close issues, delete branches, edit releases, merge PRs, or change labels.
- Prefer read-only commands first; show the target repo and object id before mutating anything.
- Do not print tokens or login config.
Common Read Commands
tea repos ls
tea issues ls
tea issues view <id>
tea pulls ls
tea pulls view <id>
tea releases ls
tea labels ls
Use tea --help and subcommand help for the installed version; flags vary.
Operating Rules
- Always identify the target remote, owner, repo, branch, issue, or PR.
- When multiple remotes exist, ask or use the one documented by the repo.
- Prefer
tea pulls viewplus localgit diff/git logbefore reviewing a PR. - For labels and milestones, preserve existing naming conventions.
- For releases, verify tag existence and changelog source before publishing.
- For automation, wrap
teain small scripts only when the command is repeated.
Review And Triage Flow
- List the relevant issues or PRs.
- Open the target item with full metadata.
- Cross-check local branch, CI status, and linked issues.
- Perform the smallest needed action.
- Report the command result and any follow-up state.
Red Flags
- command would mutate a repo inferred only from the current directory
- ambiguous login/profile
- closing or merging without showing target id
- release creation without checking tag and artifacts
- automation that assumes one Gitea host across all projects