Update existing review instead of always posting a new one #6

New Issue

2026-05-01T18:26:22Z

rodin commented

2026-05-01 18:26:22 +00:00

Problem

Every push triggers a new review, which creates a growing stack of review comments on the PR. On active PRs with many iterations, this clutters the conversation and makes it hard to find the current review state.

Proposed Solution

When posting a review, check if the same reviewer bot already has an existing review on the PR. If so, either:

Dismiss the old review and post a new one (keeps history but marks old as stale)
Edit the existing review body in-place (cleaner, single source of truth)

Implementation Ideas

Before posting, call GET /repos/{owner}/{repo}/pulls/{pr}/reviews and filter by the current reviewer username
If a previous review exists from the same bot:
- Option A: Use POST /repos/{owner}/{repo}/pulls/{pr}/reviews/{id}/dismissals on the old one, then post new
- Option B: Use PATCH /repos/{owner}/{repo}/pulls/{pr}/reviews/{id} to update the body (if Gitea supports it)
Add a --update-existing flag (default: true) so users can opt into the old behavior with --update-existing=false

Benefits

Cleaner PR threads
Single authoritative review per bot at any time
Easier to see current review state at a glance
Reduces notification spam for PR participants

## Problem Every push triggers a new review, which creates a growing stack of review comments on the PR. On active PRs with many iterations, this clutters the conversation and makes it hard to find the current review state. ## Proposed Solution When posting a review, check if the same reviewer bot already has an existing review on the PR. If so, either: 1. **Dismiss the old review and post a new one** (keeps history but marks old as stale) 2. **Edit the existing review body in-place** (cleaner, single source of truth) ## Implementation Ideas - Before posting, call `GET /repos/{owner}/{repo}/pulls/{pr}/reviews` and filter by the current reviewer username - If a previous review exists from the same bot: - Option A: Use `POST /repos/{owner}/{repo}/pulls/{pr}/reviews/{id}/dismissals` on the old one, then post new - Option B: Use `PATCH /repos/{owner}/{repo}/pulls/{pr}/reviews/{id}` to update the body (if Gitea supports it) - Add a `--update-existing` flag (default: true) so users can opt into the old behavior with `--update-existing=false` ## Benefits - Cleaner PR threads - Single authoritative review per bot at any time - Easier to see current review state at a glance - Reduces notification spam for PR participants

rodin referenced this issue from a commit

2026-05-02 03:17:03 +00:00

feat: delete previous review before posting new one (#6)

rodin referenced a pull request that will close this issue

2026-05-02 03:17:10 +00:00

feat: delete previous review before posting new one (#6) #22

aweiker closed this issue

2026-05-02 04:50:16 +00:00

aweiker referenced this issue from a commit

2026-05-02 04:50:17 +00:00

Merge pull request 'feat: delete previous review before posting new one (#6)' (#22) from feat/6-update-existing-review into main

rodin referenced this issue