work-items: preflight credits the main checkout's settings.local.json to worktrees on Windows, where approvals stay per worktree
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 72/100
Direzione di ricerca
Read plugins/work-items/skills/work/scripts/preflight.sh and its collect() function, then compare the platform-specific settings behavior described in the issue with Cases 16 and 16b in plugins/work-items/skills/work/scripts/preflight.test.sh. Add a Windows-layout test alongside those cases and update the preflight behavior to match it. Done means the main settings file is not credited for a Windows worktree and the worktree's own local settings are considered.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
The work-items preflight credits the main checkout's .claude/settings.local.json to every linked worktree. The live docs say approvals are shared that way only where Claude Code uses the repository root; on Windows and the other layouts where it does not, an approval stays with the worktree it was granted in. On those layouts the preflight reports a grant as covered that the worktree session will not have, so an unattended lane can hit a permission prompt the preflight said was covered.
Affected area / component
plugins/work-items/skills/work/scripts/preflight.sh (collect()), plugins/work-items/skills/work/scripts/preflight.test.sh
Steps to reproduce
- On Windows, put
Bash(gh pr create *)in the main checkout's.claude/settings.local.jsononly. - Run the preflight for a linked worktree (
--worktree-root <worktree>). - The preflight reports no gap for
gh pr create. - Start a session in that worktree and run
gh pr create: it prompts.
(Steps 1-3 match the existing test "Case 16" at preflight.test.sh:303; step 4 follows from the docs and was not run.)
Expected behavior
On Windows and other layouts where Claude Code does not use the repository root, the preflight reads the worktree's own settings.local.json and does not credit the main checkout's.
Actual behavior
preflight.sh:24-31and:143-146: since Claude Code v2.1.211, "don't ask again" approvals "save here (resolved through worktrees to the main checkout) and apply in every worktree of the repository, so this file is read in every mode".collect()at:343reads it unconditionally on every platform.preflight.test.sh:303-322("Case 16") asserts the main checkout's grant covers a worktree run;:324("Case 16b") asserts a worktree's own local file is excluded.- Live docs (read 2026-10-12):
- https://code.claude.com/docs/en/worktrees#what-worktrees-share-with-the-main-checkout: "On Windows and in the other cases where Claude Code doesn't use the repository root, the rule stays with that worktree."
- https://code.claude.com/docs/en/permissions#permission-system: "In some cases, such as outside a git repository or on Windows, Claude Code doesn't use the repository root."
Suggested fix
Branch on the layout: on Windows and the other non-repository-root cases listed at https://code.claude.com/docs/en/settings#where-claude-code-keeps-the-local-file-in-a-git-repository (outside a git repository, a home-directory repository root, Windows, or a root not owned by the user), read the worktree's own settings.local.json instead of the main checkout's. Add a Windows-layout case beside Case 16 and invert Case 16b for that layout.
Environment
Windows; work-items 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
- 8h 27m
- PR unite (30g)
- 957
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di melodic-software/claude-code-plugins
-
priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
melodic-software/claude-code-plugins#7351 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
agent-ready priority: high work-class: scoped
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
melodic-software/claude-code-plugins#7312 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
melodic-software/claude-code-plugins#7288 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail thresholdApertaneeds-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
melodic-software/claude-code-plugins#7286 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
melodic-software/claude-code-plugins#7282 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di melodic-software/claude-code-plugins
Issue simili
-
area:contributor-experience difficulty:easy good first issue Stellar Wave
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 2 giorni
-
package-update
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
oSoWoSo/vOid_Community_repOsitory#436 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Maki-Zeninn/stellar-router#1485 ·
I maintainer di solito rispondono entro 1 giorno
-
Pin pnpm 9 with a packageManager fieldForse già presa @Rohit-Solanki1890 l’ha presa oggi. Apertadevops dx good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
StellarLock/StellarLock#980 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
hestiacp/hestiacp#5798 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno