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

未关闭
#57 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
40/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
github, rust, tauri
领域
api, desktop-dev

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Rust
星标
3
派生
1
平均合并
9 小时 51 分钟
30 天内合并 PR
310

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。