ShockVPN/shockbot
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Resolve threads in AddressReviews mode (#266)

Browse Source 
* Add review thread resolution to AddressReviews mode

- Add thread_id to comment metadata in buildThreadBlocks
- Implement ResolveReviewThreadTool with GraphQL mutation
- Register new tool in MCP server
- Update AddressReviews mode to resolve threads after addressing feedback

Closes #227

* Fix typo: use log.warning instead of log.warn

* refactor: DRY up catch block by extracting isResolved condition

* fix lint.

* fix: avoid using any.

* fix: combining log statements around the message.

* fix(test): Adjusting snapshot.

---------

Co-authored-by: pullfrog[bot] <226033991+pullfrog[bot]@users.noreply.github.com>
Co-authored-by: Robin Tail <robin_tail@me.com>
This commit is contained in:
pullfrog[bot]
2026-02-12 15:25:21 +00:00
committed by pullfrog[bot]
co-authored by pullfrog[bot] <226033991+pullfrog[bot]@users.noreply.github.com> Robin Tail
parent 0ecb1edcdd
commit a442f766aa
5 changed files with 125 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mcp/__snapshots__/reviewComments.test.ts.snap
+1 -1
View File
@@ -11,7 +11,7 @@ exports[`formatReviewThreads > formats thread blocks with TOC and correct line n
## .github/workflows/test.yml:7 [RESOLVED]
\`\`\`\`comment author=cursor id=2544544046 review=3485940013 *
\`\`\`\`comment author=cursor id=2544544046 review=3485940013 thread=PRRT_kwDOPaxxp85iysVl *
### Bug: GitHub Actions workflow triggered for wrong branch
<!-- **High Severity** -->