Git configuration validation is too strict and does not allow empty values
When validating the Git configuration as specified in our config.toml
we require that the value set for each entry is non-empty. This is too strict, and there are valid usecases where this can make sense. This breaks for example the case where an administrator sets up a global proxy via http.proxy=http://example.com
, but then overrides it for specific subdomains via http.http://subdomain.example.com.proxy=
.