Skip to content
This repository was archived by the owner on Mar 6, 2024. It is now read-only.

update prompt #368

Merged
merged 2 commits into from
Jul 15, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down
4,456 changes: 3,078 additions & 1,378 deletions dist/index.js

Large diffs are not rendered by default.

9 changes: 4 additions & 5 deletions src/prompts.ts
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down