CommentPoller reads /repos/{repo}/issues/{index}/comments, which returns a PR's conversation comments only. Comments left on specific lines in Gitea's "Files changed" view, and the body of a submitted review, live under the pull-request reviews API (/repos/{repo}/pulls/{index}/reviews and each review's /comments). The agent never sees them, so line-level review feedback is silently ignored.
Expected: the review watch also delivers review bodies and inline comments from operator logins, with the file and line included so the executor knows where the feedback applies. The comment cursor from #68 needs to cover both sources (the ID spaces may differ, so keep one cursor per source).
Also relevant: the agent should answer inline comments inline, as a reply in the same review thread, not as a top-level PR comment. #65 (agent merges approved PRs) will need the review API anyway to see approvals.
Noticed while doing #68.
`CommentPoller` reads `/repos/{repo}/issues/{index}/comments`, which returns a PR's conversation comments only. Comments left on specific lines in Gitea's "Files changed" view, and the body of a submitted review, live under the pull-request reviews API (`/repos/{repo}/pulls/{index}/reviews` and each review's `/comments`). The agent never sees them, so line-level review feedback is silently ignored.
**Expected:** the review watch also delivers review bodies and inline comments from operator logins, with the file and line included so the executor knows where the feedback applies. The comment cursor from #68 needs to cover both sources (the ID spaces may differ, so keep one cursor per source).
**Also relevant:** the agent should answer inline comments inline, as a reply in the same review thread, not as a top-level PR comment. #65 (agent merges approved PRs) will need the review API anyway to see approvals.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Noticed while doing #68.
CommentPollerreads/repos/{repo}/issues/{index}/comments, which returns a PR's conversation comments only. Comments left on specific lines in Gitea's "Files changed" view, and the body of a submitted review, live under the pull-request reviews API (/repos/{repo}/pulls/{index}/reviewsand each review's/comments). The agent never sees them, so line-level review feedback is silently ignored.Expected: the review watch also delivers review bodies and inline comments from operator logins, with the file and line included so the executor knows where the feedback applies. The comment cursor from #68 needs to cover both sources (the ID spaces may differ, so keep one cursor per source).
Also relevant: the agent should answer inline comments inline, as a reply in the same review thread, not as a top-level PR comment. #65 (agent merges approved PRs) will need the review API anyway to see approvals.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE