Repository navigation
feat(review): make inline notes keyboard selectable - #1044
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
Greptile SummaryThis PR adds persistent keyboard focus for inline review notes and integrates notes into both semantic and rendered vertical navigation.
Confidence Score: 5/5The PR appears safe to merge; no concrete correctness, security, or repository-rule issue remains. Active-note state, navigation, action targeting, rendering, protocol parsing, and reconciliation are coherently integrated and covered by unit, component, conformance, and PTY tests. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
Input["Keyboard or mouse input"] --> Route{"Navigation type"}
Route -->|"j / k or Up / Down"| Stops["Measured vertical stops"]
Stops --> Line["Source-line cursor"]
Stops --> Note["Exact note identity"]
Route -->|"n / N"| Semantic["Semantic visible-note ordering"]
Semantic --> Note
Route -->|"Click note card"| Note
Note --> State["Review state: selection + activeNoteId"]
Line --> State
State --> Render["Diff pane rendering and minimal reveal"]
State --> Actions{"Active-note capabilities"}
Actions -->|"R"| Reply["Reply draft"]
Actions -->|"E"| Edit["Edit user note"]
Actions -->|"D"| Delete["Remove leaf note"]
Reviews (1): Last reviewed commit: "feat(review): make inline notes keyboard..." | Re-trigger Greptile |
benvinegar
force-pushed
the
feat/review-note-keyboard-selection
branch
from
September 8, 2026 00:48
2beed3f to
11a2fd6
Compare
benvinegar
force-pushed
the
feat/review-note-keyboard-selection
branch
from
September 8, 2026 01:45
11a2fd6 to
aef0240
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Inline review comments rendered between source lines, but keyboard movement skipped over them and note actions depended on mouse-only controls. This made threaded comments difficult to review and operate on from the keyboard.
Approach
j/kand Up/Down visit source lines, comments, and every reply in ordern/Nas presentation-local and resolve them from the active surface’s measured note order before dispatching validated exact-note selectionR,E, andDfor replying to, editing, and deleting the active leaf noteText/range selection remains source-line-only, and ordinary row navigation still clears note focus so line and note selection cannot be active together.
Validation
TMPDIR=/var/tmp bun run testbun run typecheckbun run lintbun run deps:checkbun test ./test/review-conformancebun test test/pty/notes.test.tsbun run test:tty-smokeTested on Linux. The PTY tests drive the real TUI for keyboard, mouse, save, thread, and narrow-layout behavior. No separate video is attached.
Release
Includes a minor Changeset for
hunkdiff.This PR description was generated by Pi using gpt-5.6-sol