Expose Git and PR actions in the UI
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 60/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
- 領域
- frontend
研究方向
Start from the channel details sidebar added in #129, which already surfaces the lane's branch, changes and newest PR, then trace where the shared Diff view instantiates CreatePrMenu — its PR-creation callbacks are defined but unwired. Map each missing action (commit, push, publish, merge, rebase, Create PR, PR review) to the existing lane/Git APIs the sidebar already calls. Done when each action is reachable from the UI and the PR-creation callbacks are connected end to end.
由索引模型根據 Issue 內容生成。
描述
Expose commit, push, publish, merge, rebase, Create PR, PR review and state, and the lane's Git state. The shared Diff view supports CreatePrMenu, but the app does not wire the PR-creation callbacks, so no Create PR action is exposed yet.
Status
The channel details sidebar (#129) now shows the lane's branch, its changes (opening the Diff tab), and the newest PR from that branch with its state and checks. Actions ask the chat's agent, which lands the lane through lane push and gh pr create, so the UI never pushes around lane.
- Create PR and Create draft PR in details and the Diff header (#472)
- Fix failed checks from the chat's failed-checks line (#472)
- Commit (#475)
- Push / update an open PR (#475)
- Rebase onto the lane's base, with
Changes.behind(#475) - Merge, once checks and reviews allow and nothing is unpushed (#475)
- Ready for review, Close, and Address review when changes are requested (#475)
- Close PR when the PR can't merge yet (#478)
- Commit, update, rebase, and the PR state actions in the Diff header (#478)
- Exercise Commit, Create PR, Update PR, Merge, and Close end to end on a disposable PR (#478)
- Exercise Address review (needs a second reviewer to request changes) and Rebase end to end
Tracked by #6. Migrated from TODO.md — Port from old Ace.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 0
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/ace2 的其他 Issue
-
documentation
難度 2/5 1-3 小時 新手友好度 76/100
githubnext/ace2#530 · 1 則留言 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
githubnext/ace2#437 ·
-
難度 4/5 3-5 天 新手友好度 35/100
githubnext/ace2#529 ·
-
難度 4/5 3-5 天 新手友好度 45/100
githubnext/ace2#528 ·
-
難度 5/5 一週以上 新手友好度 20/100
githubnext/ace2#511 ·
相似的 Issue
-
engine-rs P3 review-deferral wasm
難度 2/5 1-3 小時 新手友好度 77/100
maniator/verticopolis#1154 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
Bug
難度 2/5 1-3 小時 新手友好度 76/100
telerik/kendo-react#3861 ·
維護者通常 1 天內回覆
-
[bug]: use-mobile.ts uses pixel logic, causing UI state de-sync with Tailwind CSS rem breakpoints未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
task
難度 2/5 1-3 小時 新手友好度 72/100