A task-ground comment wrongly says a branch carries only HEAD
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 78/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
/taskbegun 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.
- Lenguaje dominante
- Go
- Estrellas
- 115
- Forks
- 14
- Merge medio
- 9 h 38 min
- PR fusionados (30 d)
- 730
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Agent-Field/CodeAF
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Agent-Field/CodeAF#1489 ·
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Agent-Field/CodeAF#1470 ·
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Agent-Field/CodeAF#1469 ·
-
area:chat bug sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1468 ·
-
area:tests bug hygiene sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Agent-Field/CodeAF#1460 ·
Todos los issues de Agent-Field/CodeAF
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
bazel-contrib/rules_go#4726 · 1 comentario ·
-
area/auto-scaling area/monitoring area/ops-productivity kind/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Type/Improvement
Dificultad 1/5 1-3 horas Aptitud para principiantes 90/100
OpenNSW/nsw-srilanka#522 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 92/100