Under the hood
Git config read failures now report a specific cause instead of silently returning nothing
What
The 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.
Why
This 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed the /config dialog changing height when switching between its tabs