Compare commits

..

No commits in common. "349378a13e44c05b2c9b86cdb270db04079a61c7" and "e8f4ca81baedfa3851d43a93ab0380a85aea8f34" have entirely different histories.

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 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
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"