forge.v1 CreateReviewCommentsRequest now carries event (COMMENT or REQUEST_CHANGES, empty means COMMENT) and body (list of findings with no line anchor). The GitHub and Gitea forge extensions in archipelago must submit one review object with that event and body instead of per-comment posts. Done when a pr-review run with a blocking finding shows a REQUEST_CHANGES review whose body lists any unanchored findings, on both forges.
Imported from beads archie-core-8i87z · GitHub #1700 · type task · priority P2 · created 2026-10-17
forge.v1 CreateReviewCommentsRequest now carries event (COMMENT or REQUEST_CHANGES, empty means COMMENT) and body (list of findings with no line anchor). The GitHub and Gitea forge extensions in archipelago must submit one review object with that event and body instead of per-comment posts. Done when a pr-review run with a blocking finding shows a REQUEST_CHANGES review whose body lists any unanchored findings, on both forges.
---
_Imported from beads `archie-core-8i87z` · GitHub #1700 · type task · priority P2 · created 2026-10-17_
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.
forge.v1 CreateReviewCommentsRequest now carries event (COMMENT or REQUEST_CHANGES, empty means COMMENT) and body (list of findings with no line anchor). The GitHub and Gitea forge extensions in archipelago must submit one review object with that event and body instead of per-comment posts. Done when a pr-review run with a blocking finding shows a REQUEST_CHANGES review whose body lists any unanchored findings, on both forges.
Imported from beads
archie-core-8i87z· GitHub #1700 · type task · priority P2 · created 2026-10-17