mnapoli Step 1: Fetch unresolved review threads and CI status
Run both helper scripts:
bash ./get-unresolved-threads.sh
bash ./get-failing-ci.sh
The first returns a JSON array of unresolved threads. Each thread has:
id— thread ID (needed to reply)path— file pathline/startLine— line numbers in the diffisOutdated— whether the diff has changed since the commentcomments.nodes[]— the comment thread (first = original comment, rest = replies), each withauthor.login,body, andurl
The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).
If there are no unresolved threads and CI is green, stop here.
Step 2: Address each issue
If there are many items, create one task per item to keep things organized.
For each unresolved review thread:
- Read the comment thread to understand the issue
- Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
- If a change is needed, make the necessary code changes
For each CI failure:
- Read the failure output to understand what broke
- Fix the code or tests to make CI pass
Step 3: Commit and push changes
After addressing all review comments and CI failures, commit your changes and push.
Step 4: Reply to each review thread
After addressing each comment, reply using the helper script:
bash ./reply-to-thread.sh "<thread_id>" "<body>" [--resolve]
- If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass
--resolveto mark the thread as resolved. - If no change was applied, briefly explain why and keep the thread unresolved (omit
--resolve) so the reviewer can reply if they disagree. - Don't be unnecessarily verbose.