Repository navigation
Tags
Tags
feat: review-thread tools — list, reply in place, resolve (v0.9.0) (#36) Unresolved PR review threads keep a PR's QA check from clearing, so board cards sat 'auto-merge pending' after a fix round (protoAgent#3745), and the agent could only post a PR-level comment — it had no way to answer a thread where it was raised or resolve it. - github_review_threads (read): a PR's review threads with PRRT_ ids, path:line, author, first comment; unresolved by default. - github_reply_thread (write, gated): addPullRequestReviewThreadReply, optional resolve. - github_resolve_thread (write, gated): resolveReviewThread / unresolveReviewThread. Thread ids are validated before gh runs; GraphQL errors surface as Error strings. Inventory docs updated (16 read / 10 write / 3 review = 29). Reported in projectManager's friction log. Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
chore: release v0.7.1 - Contents reads are GETs (#29): `github_read_file`, `github_read_pr_file`, `github_path_exists` and `github_repo_contents` passed the ref as `-f ref=`, which made `gh api` send POST, and GitHub 404s a POST to /contents. Every ref-pinned read failed; the QA panel's lanes reviewed diffs blind (pr-reviewer-plugin#118). - Adds the standard release caller (`.github/workflows/release.yml`, the reusable release-tools plugin-release workflow) so this plugin releases like the others. - uv.lock's own version entry had drifted to 0.5.0; now 0.7.1. Claude-Session: https://claude.ai/code/session_01LSRkzcPyaDrKSY7geFuGr3 Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
PreviousNext