fix: render per-comment file line instead of thread-level location

2026-04-08 23:23:19 +08:00
parent a61be1b4c4
commit d00e6bcb2c
7 changed files with 35 additions and 8 deletions
@@ -71,14 +71,15 @@ total: <files_changed> files, +<additions>, -<deletions>
 ## Review 1 (<review-state>)
 > <reviewer>

-### Comment 1.1
+### Comment <pr-index>.<comment-seq>
 <file>:<line>
 <user>:
 ```md
 <original comment body>
 ```

-### Reply 1.1.1
+### Reply <pr-index>.<comment-seq>.<reply-seq>
+<file>:<line>
 <user>:
 ```md
 <original reply body>
@@ -89,3 +90,4 @@ total: <files_changed> files, +<additions>, -<deletions>

 - Output goes to `stdout` by default; use `--out` to write a file.
 - The renderer preserves markdown-heavy comment bodies safely by adjusting code fences when needed.
+- Both `Comment` and `Reply` include their directly associated file path and line number (when provided by the API).