Skip to content

feat(review): show the pull request's own context, and allow a bare verdict - #24

Merged
fiddur merged 1 commit into
developfrom
pr-context
Aug 21, 2026
Merged

feat(review): show the pull request's own context, and allow a bare verdict#24
fiddur merged 1 commit into
developfrom
pr-context

Conversation

@fiddur

@fiddur fiddur commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Reading a diff without the description means re-deriving the intent from the code; without the existing reviews it means repeating a point someone else already made. A collapsible panel above the diff now carries the description as markdown and every existing review with its author, verdict and body.

Verified on the hardest case — a merged PR with a detached checkout:

PR #671 | description: 140 chars | existing reviews: 4
  copilot-pull-request-reviewer[bot]  COMMENTED   ## Pull request overview…
  fiddur                              DISMISSED   lgtm
  frodi-karlsson                      DISMISSED   seems to work well 👍
  frodi-karlsson                      APPROVED    (verdict only)

That surfaced something invisible before: a second reviewer, and two dismissed verdicts.

One judgement call: a COMMENTED review with an empty body is dropped, because that is what the forge records for a batch of inline comments — those arrive through the inline pull, so the row would be noise. A bodiless APPROVED or CHANGES_REQUESTED is kept, since there the verdict is the content. Both tested.

Approving no longer requires attaching anything. Only a plain comment needs a body or a comment to carry; a verdict stands on its own — enforced identically in the dialog (canSubmitReview), the route validation and createReview. The submit button relabels to Submit approve so it does not promise comments it is not sending.

And a real bug from the merged-PR fallback in #23: gh pr view resolves the PR from the current branch, so a detached checkout returned null details and every forge feature went dark — no panel, no submitting. fetchDetails now takes the PR number, threaded through from PR mode.

Also drops an esbuild.jsx block from the UI vite config that vite 8 ignores in favour of oxc, and warned about on every test run.

TDD: 3 red on canSubmitReview, 4 red on the panel, 4 red on parseReviews. 297 tests pass.

Stacked on #23.

🤖 Generated with Claude Code

https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs

…erdict

Reading a diff without the description means re-deriving intent from the code, and without
the existing reviews it means repeating a point someone else already made. A collapsible
panel above the diff now carries the description as markdown and every existing review with
its author, verdict and body.

A COMMENTED review with an empty body is dropped: that is what the forge records for a batch
of inline comments, and those arrive through the inline pull. A bodiless APPROVED or
CHANGES_REQUESTED is kept, because there the verdict is the content.

Submitting an approval no longer requires attaching anything. Only a plain comment needs a
body or a comment to carry - a verdict stands on its own, in the dialog, in the route
validation and in createReview.

Fixes a real consequence of the merged-PR checkout fallback: `gh pr view` resolves the pull
request from the current branch, so a detached checkout returned no details at all and every
forge feature went dark. Details now take the pull request number.

Drops an esbuild jsx block from the UI vite config that vite 8 ignores in favour of oxc, and
warned about on every test run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
@fiddur
fiddur changed the base branch from review-progress to develop August 21, 2026 13:36
@fiddur
fiddur marked this pull request as ready for review August 21, 2026 13:36
@fiddur
fiddur merged commit d1d57a5 into develop Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant