{"version":"2.1.281","anchor":"git-allowlist-no-lazy-fetch-and-no-advice-accepted","canonical_anchor":"git-allowlist-no-lazy-fetch-and-no-advice-accepted","heading":"git allowlist: --no-lazy-fetch and --no-advice accepted as global options","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/git-allowlist-no-lazy-fetch-and-no-advice-accepted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### git allowlist: `--no-lazy-fetch` and `--no-advice` accepted as global options\n\nClaude Code's git permission checks now recognise `--no-lazy-fetch` and `--no-advice` as git global options\n\n**What**\n\nGit 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`.\n\n**Why**\n\nGit 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."}