/hyperpower:respond
Answer every review comment against the code it points at.
Reference
/hyperpower:respond 412When to use it
Someone reviewed your pull request and you want to answer every comment properly.
What you get
A table with one row per comment: what was done, the lines that settle it, and a command the reviewer can run. Replies are drafted, and nothing is posted until you say so.
How it works
It reads every comment on the pull request, including the ones GitHub keeps apart: comments on a line, the text of a review, and the conversation tab. If any of them could not be read, it says so first, because a partial list looks exactly like a complete one.
For each comment it opens the file at that line before deciding anything, and records which files it opened. Then it gives the comment one answer:
| Answer | Means |
|---|---|
| changed | the code changed because of this comment |
| already done | the code already did what they asked, and it shows where |
| declined | read and understood, not done, with the reason |
| needs them | it cannot be settled without the reviewer |
Every changed row names the command a reviewer can run to see it for themselves. A small change is made in place. A bigger one becomes its own run.
The replies are drafted and printed. Nothing is posted, no thread is resolved, and nothing is pushed until you say post.