Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

tui3: a run's review checks are never drawn in the Tasks column (#1556 item 1)

未關閉
  • 哪裡不對？
#1,646 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
78/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
go
領域
cli, testing-qa

研究方向

Start with AddReviewCheck in internal/plandb/store.go, then inspect the Tasks-column plan listing and the counting logic in runsummary.go and runask.go. Run or add the tui3 unit case for a run with two parts and one review check. Done means the check is drawn under its part and summary counts remain correct, with checks named separately if counted.

由索引模型根據 Issue 內容生成。

描述

area:chat bug

What happened

The checks a run adds (check: <part>) exist in the plan but are never drawn in the Tasks side column, although internal/manual/chat/worker-harness.md says a run shows "its parts and their checks hanging under it". This is item 1 of #1556, split out because #1640 fixed items 2 and 4 and #1627 fixed item 3.

Replication

Deterministic (no model). A stubbed run with two parts and a review check: the plan database holds three tasks, and the side column draws two.

Where

  • AddReviewCheck in internal/plandb/store.go does not give the check its parent's chat tag, the way Add does.
  • The Tasks column's plan listing filters by that tag, so the check is dropped.
  • The two-line fix changes what runsummary.go and runask.go count, so those have to be checked in the same change.

The fix

A review check carries its parent's chat tag, so it is drawn under its part. Run summaries count parts and checks the way the manual describes.

Acceptance

  • Unit (tui3): a run with two parts and one check draws the check under its part.
  • Unit: the run summary's counts are unchanged for parts, and name checks separately if they are counted at all.
主要語言
Go
星號
115
分支
14
平均合併
9 小時
30 天內合併 PR
232

環境準備

我們還沒有檢查這個專案的環境設定檔。先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。