Skip to content

Add comment/thread and change-block navigation #1255

Open

Description

@imsardine

What do you want to change?

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.

How? (optional)

No response

Activity

  1. Ajay-Satish-01 commented on Nov 10, 2026

    @Ajay-Satish-01
    Contributor

    I would like to work on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions