Compare commits

...

1 commit

Author SHA1 Message Date
3f2bdb897a fix: Update claude to not decline pr's
Some checks failed
CI / Get Changed Files (pull_request) Successful in 14s
CI / Docker frontend validation (pull_request) Failing after 33s
CI / Backend Tests (pull_request) Failing after 1m36s
Setup Gitea Tea CLI / setup-and-login (pull_request) Successful in 2m45s
CI / prettier (pull_request) Successful in 3m16s
CI / oxlint (pull_request) Successful in 3m27s
CI / eslint (pull_request) Successful in 3m32s
CI / test-build (pull_request) Successful in 3m50s
CI / Checkstyle Main (pull_request) Successful in 3m58s
CI / Docker backend validation (pull_request) Successful in 4m47s
2025-06-01 10:36:06 +02:00

View file

@ -69,7 +69,7 @@ jobs:
Once you are done with your review, post your feedback as a reject or review on the pull request using the following exact format: Once you are done with your review, post your feedback as a reject or review on the pull request using the following exact format:
tea \"<reject or approve>\" ${PR_NUMBER} \"<your review message here>\" tea \"<comment or approve>\" ${PR_NUMBER} \"<your review message here>\"
Make sure the comment is clear, professional, and helpful. Only run the tea comment command once you're finished reviewing all changes. AND MOST IMPORTANDLY ONLY REVIEW THE DIFF FROM THE CURRENT STATE TO THE MAIN BRANCH TO GET THAT USE GIT DIFF Make sure the comment is clear, professional, and helpful. Only run the tea comment command once you're finished reviewing all changes. AND MOST IMPORTANDLY ONLY REVIEW THE DIFF FROM THE CURRENT STATE TO THE MAIN BRANCH TO GET THAT USE GIT DIFF
You may also use the tea cli to find out various things about the pull request You may also use the tea cli to find out various things about the pull request