Compare commits

..

No commits in common. "fa67dd5ebf6033049d8d277b9e8293e299426ae7" and "4960b5966fefc237a5895db3888cc31e81e91254" have entirely different histories.

View file

@ -1,11 +1,11 @@
name: Claude PR Review name: Setup Gitea Tea CLI
on: on:
pull_request: pull_request:
types: [opened, synchronize] # Runs on new PRs and updates types: [opened, synchronize] # Runs on new PRs and updates
jobs: jobs:
claude-code: setup-and-login:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Checkout code - name: Checkout code
@ -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 \"<comment 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 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