{"version":"2.1.265","anchor":"git-config-reads-now-report-a-specific-failure-cause-instead","canonical_anchor":"git-config-reads-now-report-a-specific-failure-cause-instead","heading":"Git config reads now report a specific failure cause instead of returning null","tier":"internal","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/git-config-reads-now-report-a-specific-failure-cause-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Git config reads now report a specific failure cause instead of returning null\n\nGit config read failures now report a specific cause instead of silently returning nothing\n\n**What**\n\nThe internal helper that reads a repository's `.git\/config` file (used, for example, to figure out the remote repository's identifier) now returns a structured result with `{ok, cause}` when it fails, instead of just returning null. The possible causes are `pointer_file`, `read_failed`, `unsafe_path`, `not_a_file`, and `oversize`.\n\n**Why**\n\nThis makes failures to read git configuration easier to diagnose, since the specific reason (such as an unsafe file path or a file that's too large) is now distinguishable instead of being an opaque failure.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}