Compare commits

...

2 commits

Author SHA1 Message Date
1de660d0e2
Merge pull request 'fix: Fix claude to always use tea command to review' (!248) from claude/use-tea-cli into main
Reviewed-on: #248
Reviewed-by: Claude <claude@kjan.email>
2025-06-01 10:30:51 +00:00
5d5c27827b fix: Fix claude to always use tea command to review
All checks were successful
CI / Get Changed Files (pull_request) Successful in 8s
CI / eslint (pull_request) Successful in 30s
CI / oxlint (pull_request) Successful in 30s
CI / Docker frontend validation (pull_request) Successful in 32s
CI / prettier (pull_request) Successful in 41s
CI / Docker backend validation (pull_request) Successful in 16s
CI / test-build (pull_request) Successful in 1m6s
CI / Checkstyle Main (pull_request) Successful in 1m17s
CI / Backend Tests (pull_request) Successful in 1m54s
Setup Gitea Tea CLI / setup-and-login (pull_request) Successful in 1m18s
2025-06-01 12:24:42 +02:00

View file

@ -104,8 +104,8 @@ jobs:
IMPORTANT GUIDELINES:
- You MUST use the 'tea' CLI for all Gitea interactions.
- You MUST use the tea cli to comment on the PR so the user gets a response.
- For PR reviews, ALWAYS analyze the diff. Make sure to mention specific files and line numbers.
- Be precise with 'tea' commands. If ambiguous, ask for clarification using \`tea pr comment ...\`.
- Execute only necessary 'tea' command(s).
- Ensure reviews are professional, constructive, and helpful.
"