Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Closing a filtered task tells people to search in tasks instead of Sessions

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go

调研方向

Start in internal/tui3/taskrowverbs.go at taskRowArchive, then read internal/tui3/place_sessions.go to follow how the notice is rendered. Run make demo-home and reproduce the filtered close flow in Sessions. Done means the notice names Sessions, reveals closed results for empty and matching filters, includes e2e and unit coverage, and updates the Sessions manual and invalidates record.

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

描述

area:chat bug sev:papercut

Seen on dev@debffabf6. Surfaced while verifying #1425; not introduced by it.

What happened

After a task is closed under a Sessions filter, the notice says task closed · find it by typing its name in tasks. The current place is called sessions, and the name may already be typed in its filter. The notice predates #1425; git log -S traces the string to the older Home-navigation change.

Replication

Deterministic (no model). Use make demo-home, open Sessions, filter to a task by its name, and close that task. The filter remains populated, but the notice tells the person to type its name in tasks.

Where

internal/tui3/taskrowverbs.go:97 at dev@debffabf6, taskRowArchive, sets the stale notice. internal/tui3/place_sessions.go renders it on the Sessions place.

The fix

Name Sessions, and when the filter already contains the task name, say how to reveal closed results rather than instructing the same typing again.

Acceptance

  • e2e: closing a filtered task in codeaf chat gives a notice naming sessions and an action that actually reveals the closed task.
  • Unit: notice cases cover empty and already-matching filters.
  • Update the Sessions manual and record the retired wording in invalidates.
主要语言
Go
星标
115
派生
14
平均合并
9 小时 38 分钟
30 天内合并 PR
749

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 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 摘要。