{"version":"2.1.307","anchor":"git-config-include-detection-added","canonical_anchor":"git-config-include-detection-added","heading":"Claude Code can check whether a repository's git settings pull in other files","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/git-config-include-detection-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Claude Code can check whether a repository's git settings pull in other files\n\nA new check looks in a repository's `config` and `config.worktree` files for an `[include` section\n\n**Unclear.** What Claude Code does when it finds an include section is not stated.\n\n**What**\n\nGit keeps per-repository settings in files named `config` and `config.worktree`. An `[include]` section in those files tells git to load more settings from another file. Claude Code can now read both files and report whether either has such a section. If one of them cannot be read, the answer is left unknown.\n\n**Why**\n\nOn its own this changes nothing you see; it gives Claude Code a way to tell when a repository's git settings come partly from somewhere else.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}