lockdown --apply --recursive errors on first existing file instead of continuing #124
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Symptom
coily lockdown --apply --recursive(without--replace) errors on the first repo that already has a.claude/settings.jsonand stops. The recursion-root canonical-deny merge into<root>/.claude/settings.local.jsonstill happens as a side-effect, but the rest of the recursion does not run.Expected: in recursive mode, "refuse on existing" should be per-target (skip and continue), not fatal for the whole recursion.
--replaceis the explicit opt-in for overwriting;--applyalone should be safe to point at a tree where most repos are already stamped.Repro
Context
Surfaced during a sweep to renormalize per-repo settings.json across the workspace after drift. The workaround was
--apply --replace, but that's a bigger hammer than the user wanted in some contexts.