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

A task-ground comment wrongly says a branch carries only HEAD

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the comment at internal/session/task_run.go:8308 and snapshotRung in internal/session/groundladder.go:789, then run the existing grounded-task fixture with dirty tracked and untracked files. Update the comment and manual to explain the repository ground and the later landing step, and add the stated e2e or structural protection while recording the assumption in invalidates.

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

描述

area:session bug hygiene sev:papercut

Found on santos/dev2 at 008363c98 (#1410). On dev@debffabf6 too.

What happened

The source comment WHAT THE BRANCH CARRIES IS HEAD AND NOTHING ELSE is false for repository grounds. snapshotRung carries uncommitted and untracked files into the task copy. The stale comment led a reviewer to deny behavior the manual correctly describes.

Replication

Deterministic (no model). Read cutTaskWorktree's comment, then run the existing grounded-task fixture with a modified tracked file and an untracked file before carving. Inspect the copy: both are present. git grep -n 'WHAT THE BRANCH CARRIES' origin/dev -- internal/session/task_run.go finds the same comment on dev.

Where

internal/session/task_run.go:8308 at 008363c98 contains the claim; internal/session/groundladder.go:789 carries the snapshot. On dev, the comment is at internal/session/task_run.go:8301.

The fix

Describe what the repository ground actually contributes to the branch and name the separate step that later lifts inherited work out of a landing.

Acceptance

  • e2e: a grounded /task begun with a dirty tracked file and an untracked file sees both in its copy while leaving the person's edits uncommitted.
  • Unit: a structural comment check or grounded-task assertion protects the corrected account.
  • Keep the manual consistent and record the corrected assumption 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 摘要。