{"version":"2.1.221","anchor":"sandboxed-shells-inherit-git-safe-directory-settings","canonical_anchor":"sandboxed-shells-inherit-git-safe-directory-settings","heading":"Sandboxed shells inherit git safe.directory settings","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/sandboxed-shells-inherit-git-safe-directory-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Sandboxed shells inherit git safe.directory settings\n\nGit commands inside a sandbox no longer complain about dubious ownership of your repo.\n\n**What**\n\nGit commands run inside a sandbox no longer complain about dubious ownership.\n\n**Details**\n\n- The bubblewrap launcher and the other sandbox command builder compute git config env pairs from the sandbox's safe dirs and inject them as `--setenv` or `KEY=VALUE` entries.\n- The Windows path adds `gitSafeDirectories` to the safe-dir list.\n\n**Evidence**\n\n`gitSafeDirectories`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}