fix(forge): pr view --comments shows formal reviews and inline feedback #5
No reviewers
Labels
No labels
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Tooling!5
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Tooling:fix/pr-view-reviews"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
forge.py pr view N --commentsonly showed the discussion thread. A reviewer's verdict (for example "request changes") and the inline comments explaining it were not shown, so someone following review feedback from the command line could see that a PR was blocked but not why.What changed
scripts/forge.py:pr view N --commentsnow also prints each submitted review (verdict, summary, commit, marked dismissed/stale) and its inline comments (file and position, marked resolved, with links). Discussion, reviews and inline comments are all paged, overlapping entries are shown once, and paging stops when a page adds nothing new (the server repeats entries on some endpoints). Drafts and unanswered review requests are left out.issue viewis unchanged.tests/test_forge_pr.py: eight checks for the output, overlap, state filtering, locations, paging with server caps of 20 and 50, ignored page numbers, unchanged default output and API failure.docs/forge.md: describes the added output and paging.Ported from Longshot#310 by monsterlag, since forge.py now lives in Tooling (Tooling#1). The code is theirs; only the context lines were adapted to Tooling's layout.
Testing
No tests were run on this PC: not
tests/run_all.py, not a single check. The ported tests were run by the original author against Longshot's copy of the file (see Longshot#310); they have not been run against Tooling's copy, so please runpython -I -B tests/run_all.pybefore merging.🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.