update prompt (#368)

coderabbitai · Jul 15, 2023 · 9ac127d · 9ac127d
1 parent 1caf00f
commit 9ac127d
Show file tree

Hide file tree

Showing 3 changed files with 3,085 additions and 1,385 deletions.
diff --git a/action.yml b/action.yml
@@ -124,9 +124,10 @@ inputs:
         and is aware of their implications on the entire system. Instead of 
         making generic comments about potential impacts on the system, focus 
         on providing specific, objective insights based on the code itself. 
-        Do not question the developer's intention behind the changes or caution 
+      - Do not question the developer's intention behind the changes or caution 
         them to ensure that their modifications do not introduce compatibility
-        issue with other dependencies.
+        issues with other dependencies.
+      - Never ask the developer to review the changes.
   summarize:
     required: false
     description: 'The prompt for final summarization response'

diff --git a/dist/index.js b/dist/index.js
diff --git a/src/prompts.ts b/src/prompts.ts
@@ -162,13 +162,12 @@ hunk is of the format \`<line_number><colon><whitespace>\`.
 - Replacement suggestions should be complete, correctly formatted and without
   the line number annotations. Each suggestion must be provided as a separate 
   review section with relevant line number ranges.
-- If needed, suggest new code snippets using the correct language identifier in the 
-  fenced code blocks. These snippets may be added to a different file 
+- If needed, suggest new code snippets using the correct language identifier 
+  in the fenced code blocks. These snippets may be added to a different file 
   (e.g. test cases), or within the same file at locations outside the provided
   hunks. Multiple new code snippets are allowed within a single review section.
-- If there are no substantive issues detected at a line range and/or the 
-  implementation looks good, you must respond with the comment "LGTM!" and 
-  nothing else for the respective line range in a review section.
+- IMPORTANT: If there are no issues found on a line range, you must only 
+  respond with the text \`LGTM!\` for that line range in the review section. 
 - Reflect on your comments and line number ranges before sending the final 
   response to ensure accuracy of line number ranges and replacement snippets.