{"version":"2.1.315","anchor":"new-infoexclude-writer-with-tengu-moonlit-locket","canonical_anchor":"new-infoexclude-writer-with-tengu-moonlit-locket","heading":"Safer way to add entries to a repository's git exclude file","tier":"internal","area":"Git Integration","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/new-infoexclude-writer-with-tengu-moonlit-locket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Safer way to add entries to a repository's git exclude file\n\nClaude Code can now add entries to `.git\/info\/exclude`, skipping links and files over 1 MiB, and saying why\n\n**Unclear.** It is not clear when Claude Code writes to a repository's exclude file, or what it adds there.\n\n**What**\n\n`.git\/info\/exclude` is a per-repository list of files git should ignore. Unlike `.gitignore`, it is not shared with others. Claude Code can now append entries to it. It refuses, and states the reason, when:\n\n- the file or its folder is a symlink, which is a shortcut pointing somewhere else\n\n- the file has more than one hard link, meaning the same file appears under more than one name\n\n- the file is larger than 1 MiB\n\nWhen a remote setting is on and the runtime supports it, Claude Code uses a stricter method. This method guards against a folder being swapped out while it writes.\n\n**Why**\n\nThese checks stop a write to the exclude file from being redirected to some other file on your machine.\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}