Desktop: submit GitHub PR reviews (comment / approve / request changes)

Abierto
#57 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
github, rust, tauri
Área
api, desktop-dev

Línea de trabajo

Start by locating the PR tab's Files view and the existing Changes comment UI it should reuse, then trace how the desktop app currently shells out to gh api for GitHub calls. Map the pending-review flow: collect line comments locally, submit one Comment/Approve/Request changes call, then handle inline thread display and resolution. Done when the three acceptance criteria hold: a two-comment Request changes review appears as one review on GitHub, existing threads render and resolve inline, and no auth beyond gh is needed.

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

Descripción

area: desktop status: needs-triage type: feature

Problem

The Pull request tab shows the timeline and checks, but reviewing still needs github.com: you cannot leave review comments or approve.

Evidence

From research on parallel-agent desktops and worktree tools, this is a recurring user request:

A recurring request across agent-workspace and parallel-agent tools, with high upvote counts in their public trackers.

Proposed behavior

  • In the PR tab's Files view, add line comments (reuse the Changes comment UI) into a pending review.
  • Submit as Comment / Approve / Request changes via gh api.
  • Reply/resolve existing review threads; Send to agent on a thread.

Acceptance criteria

  • A review with 2 line comments + Request changes appears on GitHub as one review.
  • Existing threads show inline and can be resolved.
  • Works without extra auth beyond gh.
Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

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 codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.