Show the Reviewed Commit Range in Dashboard Job Details

Abierto
#183 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
62/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Trace the job detail API response and the dashboard job detail page, then read the existing SHA and diff UI patterns. Expose previousCommitSha and the head SHA for incremental jobs and display their range; full reviews should show no additional range. Run the listed typecheck, test, and lint commands to check completion.

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

Descripción

enhancement good first issue

Goal

Show the reviewed commit range for incremental jobs in the dashboard job details.

Background

Incremental reviews only cover a commit range, so users need to see which range was reviewed to interpret the findings correctly. The job record already stores previousCommitSha and the head SHA.

This sub-issue is part of the parent issue: incremental reviews on synchronize events.

What to Build

  • Expose previousCommitSha (and the reviewed range) through the job detail API response
  • In the dashboard job detail page, display the reviewed commit range when the job was incremental (e.g. "Reviewed changes from abc1234 to def5678"), and nothing extra for full reviews
  • Keep the display consistent with the existing SHA/diff UI patterns

Done When

  • Job detail API includes the incremental review range
  • Dashboard shows the commit range for incremental jobs and nothing new for full reviews
  • UI matches existing dashboard styling
  • npm run typecheck, npm test, and npm run lint all pass
Lenguaje dominante
TypeScript
Estrellas
125
Forks
23
Merge medio
2 d 13 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devarshishimpi/codra

Todos los issues de devarshishimpi/codra

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.