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

Commit c546723

Browse files
authored
comment on sub ranges (#126)
<!-- This is an auto-generated comment: release notes by openai --> ### Summary by OpenAI Release Notes: - New Feature: Modify the format of review comments for a GitHub action. The new format allows commenting on sub-line ranges and suggests exact code replacements instead of diff format. > "Code reviews made easy, > With sub-line ranges so breezy. > Exact code replacements suggested, > Reviewers' feedback now perfected." <!-- end of auto-generated comment: release notes by openai -->
1 parent 4a2505e commit c546723

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

action.yml

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -192,25 +192,26 @@ inputs:
192192
$patches
193193
194194
Your review must consist of comments in the below format
195-
with a separator between review comments. Any other
195+
with a separator between review comments Any other
196196
commentary outside of this format will be ignored and will not
197-
be read by the parser. Make sure to use the line numbers exactly
198-
as provided above -
197+
be read by the parser -
199198
<start_line-end_line>:
200199
<review>
201200
---
202-
<start_line-end_line>:
201+
<replace_start_line-replace_end_line>:
203202
<review>
204203
```suggestion
205-
<replacement code from start_line>
204+
<new code from replace_start_line to replace_end_line>
206205
```
207206
---
208207
...
209208
210-
The replacement code you suggest must not be in the diff format and
211-
must the exact code that will replace existing code from the start_line.
212-
The suggestion must include context lines from diff hunk even if they
213-
are unchanged.
209+
Make sure your comments are not outside the line ranges in the changes,
210+
though you can comment on sub-line ranges. If you want to suggest code
211+
changes, the replacement code you suggest must not be in the diff format
212+
and must be exact code that will replace existing code between
213+
<replace_start_line> and <replace_end_line> based in line number in the
214+
new file.
214215
215216
Reflect on the provided code at least 3 times to identify any
216217
bug risks or provide improvement suggestions in these diff hunks.

0 commit comments

Comments
 (0)