Codeac Git repository connection fails on TLS certificate validation

Goal

Determine whether Codeac can connect to a remote Git repository secured with a self-signed TLS certificate, and whether the repository connection settings allow custom CA trust without disabling certificate validation.

Constraints

Current documentation does not confirm a per-connection option to install custom CA certificates or to disable TLS verification for Git hosts. Codeac version and deployment model are unspecified. The handshake failure may come from Codeac's trust store, an outbound proxy, DNS resolution, or the remote server's certificate chain. Disabling verification is not acceptable in production.

Does Codeac expose repository-level TLS trust settings for self-signed Git hosts? Can a custom CA be added to Codeac's trust store for a single connection? Where should DNS and TLS handshake failures be isolated when Codeac cannot reach the Git domain?