Update cr.yml

.github/workflows/cr.yml

@@ -10,25 +10,23 @@ on:
 
 jobs:
   test:
-    # if: ${{ contains(github.event.*.labels.*.name, 'gpt review') }} # Optional; to run only when a label is attached
+    # if: ${{ contains(github.event.*.labels.*.name, 'gpt review') }}  # Optional; to run only when a label is attached
     runs-on: ubuntu-latest
     steps:
       - uses: anc95/ChatGPT-CodeReview@main
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          # Optional
           LANGUAGE: Chinese
           OPENAI_API_ENDPOINT: https://api.openai.com/v1
-          MODEL: gpt-3.5-turbo # https://platform.openai.com/docs/models
-          PROMPT: # example: Please check if there are any confusions or irregularities in the following code diff:
-          top_p: 1 # https://platform.openai.com/docs/api-reference/chat/create#chat/create-top_p
-          temperature: 1 # https://platform.openai.com/docs/api-reference/chat/create#chat/create-temperature
+          MODEL: gpt-3.5-turbo
+          PROMPT: Please check if there are any confusions or irregularities in the following code diff
+          top_p: 1
+          temperature: 1
           max_tokens: 10000
-          MAX_PATCH_LENGTH: 10000 # if the patch/diff length is large than MAX_PATCH_LENGTH, will be ignored and won't review. By default, with no MAX_PATCH_LENGTH set, there is also no limit for the patch/diff length.
-          IGNORE_PATTERNS: /node_modules,*.md # glob pattern or regex pattern to ignore files, separated by comma
-          INCLUDE_PATTERNS: *.js,*.ts # glob pattern or regex pattern to include files, separated by comma
-
-          # IF you are using azure openai
-          AZURE_API_VERSION: xx
-          AZURE_DEPLOYMENT: xx
+          MAX_PATCH_LENGTH: 10000
+          IGNORE_PATTERNS: /node_modules,*.md
+          INCLUDE_PATTERNS: *.js,*.ts
+          # For Azure OpenAI (optional)
+          # AZURE_API_VERSION: "2023-05-15"
+          # AZURE_DEPLOYMENT: "your-deployment-name"