Sandbox exclusion git merge --ff-only * admits options and has no ask rule #214
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?
Seen at
99fc8652bb,.claude/settings.json(
sandbox.excludedCommands), added byadb02f0fordeliver/land.md'slanding step.
Options pass the exclusion. The
*matches any trailing arguments,options included. A later merge option overrides
--ff-only, and othermerge options read files, so a command matching the exclusion can run
outside the sandbox past the
Readrules on secret files and exposetheir content through git's output.
No ask rule. Where a developer's own settings allow
git merge, anexcluded merge in the main checkout runs unsandboxed without a prompt
and can replace the policy files and the hook scripts that the
PreToolUse hooks then run outside the sandbox.
Smallest fix: exclude only
git merge --ff-only --end-of-options *,give
land.mdthe same form (git 2.48 and later accept it), and addBash(git merge --ff-only *)topermissions.ask. With--end-of-options, git treats every later argument as a revision andrefuses an option there.