{"version":"2.1.307","anchor":"runner-git-proxy-sanitize-writes-an-ignore-rule-for-settings","canonical_anchor":"runner-git-proxy-sanitize-writes-an-ignore-rule-for-settings","heading":"Runner sessions now tell git to ignore .claude\/settings.local.json","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/runner-git-proxy-sanitize-writes-an-ignore-rule-for-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Runner sessions now tell git to ignore .claude\/settings.local.json\n\nWhen a runner resets its git setup for a session, it now writes a git ignore rule so .claude\/settings.local.json is not committed by accident\n\n**What**\n\nA runner is a copy of Claude Code that carries out sessions on someone's behalf, often on a separate machine. When it resets its home-level git setup at the start of a session (git's own settings, kept outside the project folder), it now also writes an `ignore` file into git's configuration folders. That file tells git to skip `.claude\/settings.local.json`, the file that holds your personal, machine-only Claude Code settings.\n\nBefore, the runner only removed the old configuration and restored its saved copy, and wrote no ignore rule. If writing the new file fails, Claude Code logs a warning that git may not ignore `.claude\/settings.local.json` in this session.\n\n**Why**\n\nA command such as `git add -A` stages every changed file in a project. Without the ignore rule it could pick up your local settings file and commit it with your work. If you see the warning, check what you are about to commit before you push.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}