github / github/app

Add next/previous navigation for comments in Changes/Diff view

Abierto
#1,011 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Requests and ideas
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.1k
Forks
153
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

## Problem

When reviewing a session's Changes (diff) view and leaving comments — including unresolved comments and back-and-forth conversations with the LLM — there's no quick way to jump between them. I end up scrolling up and down the diff hunting for my open threads, which gets painful on larger changes.

## Proposed feature

Add explicit **Previous / Next comment** navigation in the Changes / diff UI. Ideally:

- Visible UX affordance (e.g., up/down arrow buttons in a small floating control, or buttons in the file header) — there appears to be room for it.
- Jumps between all comment threads in the current diff (or scoped to unresolved / open threads).
- Keyboard shortcuts as well (e.g., `j`/`k` or `n`/`p`). If these already exist, they're not discoverable — surfacing them in the UI would help.
- Bonus: a small counter like `2 of 7` so you know where you are in the list of threads.

## Why it matters

- Reviewing my own comments and the LLM's responses is a core part of the iteration loop.
- Scrolling to find threads breaks flow, especially when a session has produced a large diff.
- Discoverable Prev/Next controls make the review surface feel much more like a real code review tool.

## Notes

Filed via Copilot CLI on behalf of @cirvine-MSFT.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by locating the Changes/diff view and the code that renders comment threads. Define the navigation scope, then verify that visible Previous/Next controls move through the threads and that the optional keyboard shortcuts and position counter behave consistently.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
desktop
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.