Git global options are the flags you write between git and the subcommand, as in git --no-advice status. Claude Code keeps a list of them so that, when it checks whether a git command is allowed, it can skip past them and find the real subcommand. --no-lazy-fetch and --no-advice are now on that list. One check that uses the list is the one for rev-parse --git-dir.
Why
Git commands that include either flag are now read correctly when Claude Code works out which subcommand is being run, instead of the flag being mistaken for the subcommand.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed sandbox excludedCommands entries not matching git rev-parse --git-dir, programs named like shell builtins, and commit messages…
