You'll notice
Directory sync's git-config safety checks now also refuse configs with too many hooks/filters or oversized files
What
Directory 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:
- the configuration defines more hooks and filter drivers than directory sync is able to switch off
- a config file is larger than 1 MiB
- a config file is a pipe or device rather than a regular file
Why
These 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.