{"version":"2.1.277","anchor":"directory-syncs-git-config-safety-limits-tightened-and-made","canonical_anchor":"directory-syncs-git-config-safety-limits-tightened-and-made","heading":"Directory sync's git-config safety limits tightened and made more specific","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/directory-syncs-git-config-safety-limits-tightened-and-made","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Directory sync's git-config safety limits tightened and made more specific\n\nDirectory sync's git-config safety checks now also refuse configs with too many hooks\/filters or oversized files\n\n**What**\n\nDirectory sync already refused to proceed when a repository's git configuration was unreadable or exceeded limits on include-chain depth or file count. It now also refuses when:\n\n- the configuration defines more hooks and filter drivers than directory sync is able to switch off\n\n- a config file is larger than 1 MiB\n\n- a config file is a pipe or device rather than a regular file\n\n**Why**\n\nThese additions close gaps where a git configuration could reference more hooks and filters than directory sync could safely disable, or use unusual file types\/sizes, reducing the risk of directory sync running with configuration it can't fully control.\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}