Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

session-flow: continue-in-background dirty-tree gate ignores worktree.bgIsolation

Aperta Adatta ai principianti
  • Qualcosa non va?
#7,288 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
76/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
git, shell
Ambito
tooling

Direzione di ricerca

Leggi plugins/session-flow/skills/continue-in-background/SKILL.md, in particolare il passaggio 1, « Dirty-tree gate », e confronta il modo in cui il plugin source-control legge l’impostazione in plugins/source-control/hooks/worktree-create-gate.sh. Aggiorna il controllo e il rapporto di avvio per tenere conto di worktree.bgIsolation quando è impostato su none; verifica che il motivo del rifiuto e l’avviso corrispondano al comportamento previsto dall’issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-triage priority: medium

Summary

/session-flow:continue-in-background's dirty-tree gate assumes a background session always moves into an isolated git worktree before editing, unless the current session is already in a linked worktree. The worktree.bgIsolation setting can turn that isolation off, and then the background session edits the working copy directly. The gate does not read the setting, so its reasoning and outcome are wrong in that configuration.

Affected area / component

plugins/session-flow/skills/continue-in-background/SKILL.md (step 1, "Dirty-tree gate")

Steps to reproduce

  1. In a git repository, set "worktree": {"bgIsolation": "none"} in .claude/settings.json.
  2. Leave an uncommitted change in the checkout.
  3. Run /session-flow:continue-in-background.

Expected behavior

The gate accounts for worktree.bgIsolation. With isolation off, the launched session sees the uncommitted changes, so the "changes won't carry over" reason for refusing does not apply. The real risk is different: the background session and the user would edit the same checkout at the same time, and the launch report should say so.

Actual behavior

  • SKILL.md:124-130: "Background sessions move into an isolated git worktree (a fresh checkout) before editing files (https://code.claude.com/docs/en/agent-view), so OTHER uncommitted changes in this checkout would NOT carry into the launched agent's edits. Any such changes → do NOT launch". The only exception is a session already inside a linked worktree.
  • Live docs, https://code.claude.com/docs/en/agent-view#how-file-edits-are-isolated (read 2026-10-12): "To turn off worktree isolation for a repository where git worktrees are impractical, set worktree.bgIsolation to "none". Background sessions then edit your working copy directly without moving into a worktree first." The same section lists other skip cases (a session moved to the background with /background, a write outside the working directory).
  • Nothing in plugins/session-flow/ mentions bgIsolation (grep -rn bgIsolation plugins/session-flow returns nothing). The source-control plugin already names the setting (plugins/source-control/hooks/worktree-create-gate.sh:64).

Suggested fix

Read the effective worktree.bgIsolation value before the dirty-tree check. When it is "none", skip the "changes won't carry over" refusal and instead warn that the launched session will edit this checkout in place, alongside the user. This is a gate-logic change, not a pointer fix.

Environment

session-flow on main as of 2026-10-12.

Found during the upstream-pointer sweep (PRs #7061-#7274).

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
6h 42m
PR unite (30g)
902

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.