| name | tea |
| description | Gitea/Forgejo CLI and API usage. Use when working with tea CLI commands or making direct API calls to Gitea/Forgejo instances.
|
| allowed-tools | Bash(tea:*),Bash(teaapi:*) |
Tea CLI and Gitea API
Guidelines for working with Gitea/Forgejo using the tea CLI and direct API calls.
API Documentation
OpenAPI/Swagger specification: https://gitea.kotel.app/swagger.v1.json
Use WebFetch to retrieve endpoint details when needed.
Tea CLI Commands
Common tea commands for repository management:
tea repo list
tea repo view owner/repo
tea pr list
tea pr view NUMBER
tea issue list
tea issue view NUMBER
tea release list
Direct API Access
Use teaapi to make authenticated API calls with token redaction:
teaapi curl https://gitea.kotel.app/api/v1/user
teaapi curl https://gitea.kotel.app/api/v1/repos/owner/repo
teaapi curl -X POST -d '{"title":"test"}' https://gitea.kotel.app/api/v1/repos/owner/repo/issues
The teaapi wrapper:
- Injects the token from tea config as
Authorization: token <TOKEN>
- Redacts the token value from all output
- Blocks DELETE requests by default (use
--allow-delete flag to permit, requires approval)
- Supports all curl options
Common API Endpoints
teaapi curl https://gitea.kotel.app/api/v1/user
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/branches
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/pulls
teaapi curl https://gitea.kotel.app/api/v1/repos/OWNER/REPO/issues
teaapi curl "https://gitea.kotel.app/api/v1/repos/search?q=QUERY"
teaapi curl -X POST -H "Content-Type: application/json" \
-d '{"title":"Issue title","body":"Description"}' \
https://gitea.kotel.app/api/v1/repos/OWNER/REPO/issues
teaapi curl -X POST -H "Content-Type: application/json" \
-d '{"title":"PR title","head":"branch","base":"main"}' \
https://gitea.kotel.app/api/v1/repos/OWNER/REPO/pulls