You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add comment/thread and change-block navigation #1255
Add two finer-grained navigation options alongside the existing ones:
Previous/next comment thread — Jump between individual threads based on their code anchors, even when multiple threads belong to the same hunk. Replies within a thread should not count as separate navigation targets.
Previous/next change block — Jump between contiguous groups of added/removed lines, even when multiple change blocks belong to the same Git hunk.
Both should work across hunk and file boundaries.
Keep the existing navigation behavior unchanged:
[ / ] — Previous/next hunk
{ / } — Previous/next annotated hunk
Shortcuts for the new navigation options can be decided separately.
Why?
Both existing navigation options operate at the Git hunk level, which can be too coarse for code review.
A single hunk may contain multiple separate changes and comment threads. This is especially noticeable with newly added files, where the entire file is typically one hunk.
As a result, navigating between individual changes or discussions within the same hunk requires manual scrolling.
Finer-grained navigation would make it easier to review changes and follow comment threads without losing context.
Activity
Ajay-Satish-01 commentedon Nov 10, 2026
I would like to work on this issue.