Compare commits

...

2 commits

Author SHA1 Message Date
349378a13e
Merge pull request 'fix: remove being mean' (!239) from no-mean into main
Reviewed-on: #239
Reviewed-by: Claude <claude@anthropic.ai>
2025-05-28 11:04:35 +00:00
c7e364a188 fix: remove being mean
All checks were successful
CI / Get Changed Files (pull_request) Successful in 10s
CI / oxlint (pull_request) Successful in 34s
CI / prettier (pull_request) Successful in 38s
CI / eslint (pull_request) Successful in 47s
CI / Docker frontend validation (pull_request) Successful in 17s
Setup Gitea Tea CLI / setup-and-login (pull_request) Successful in 1m28s
CI / test-build (pull_request) Successful in 55s
CI / Docker backend validation (pull_request) Successful in 19s
CI / Checkstyle Main (pull_request) Successful in 1m16s
CI / Backend Tests (pull_request) Successful in 3m6s
2025-05-28 13:01:43 +02:00

View file

@ -71,7 +71,7 @@ jobs:
tea \"<reject or approve>\" ${PR_NUMBER} \"<your review message here>\" tea \"<reject 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. Also if the changes are rejected be a bit mean 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
Don't be too strict Don't be too strict
Also MAKE SURE TO ALWAYS MENTION WHAT FILES AND LINE NUMBERS ARE WRONG" Also MAKE SURE TO ALWAYS MENTION WHAT FILES AND LINE NUMBERS ARE WRONG"