Compare commits
1 Commits
main
...
author-replies
| Author | SHA1 | Date | |
|---|---|---|---|
| 78dcb3a2b3 |
@@ -31,9 +31,11 @@ about to post, whether you reviewed yourself or relayed a reviewer subagent. Its
|
|||||||
first line must be exactly the template's verdict and nothing else: `Yes`, `No`,
|
first line must be exactly the template's verdict and nothing else: `Yes`, `No`,
|
||||||
or `With fixes`. `Yes` approves and the other two request changes; any other
|
or `With fixes`. `Yes` approves and the other two request changes; any other
|
||||||
first line is posted as a plain comment, which wastes the run. Minor issues
|
first line is posted as a plain comment, which wastes the run. Minor issues
|
||||||
alone never block. When the verdict is not `Yes`, the second line names what
|
alone never block, and neither does a finding the author has answered in the
|
||||||
must change in one line, addressed to the author; the author's own agent picks
|
comment history below as intended or a false alarm, once the code or docs make
|
||||||
the fixes up, so never ask `@bot` to make them. For UI changes, check that the
|
that clear. When the verdict is not `Yes`, the second line names what must
|
||||||
|
change in one line, addressed to the author; the author's own agent picks the
|
||||||
|
fixes up, so never ask `@bot` to make them. For UI changes, check that the
|
||||||
result is aligned, clean, and pixel-perfect, and that included screenshots prove
|
result is aligned, clean, and pixel-perfect, and that included screenshots prove
|
||||||
the intended result was achieved.
|
the intended result was achieved.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user