Is it possible to modify MettleCI's Git connection timeout?

MettleCI uses a 30-second timeout which is not exposed as a user configurable option.

If your Git server can't respond to a connection request within 30s then this is a symptom of a significant issue present in your network or Git software configuration. Boosting the connection timeout in MettleCI (even if we made it possible) is highly unlikely to resolve the issue.

The number of Git repositories, or the size of those repositories, will not impact the time taken to establish a connection. The ‘Timeout’ terminology used in the MettleCI error messages is purely because Workbench gave up waiting for a response. You'll get the same ‘timeout’ error when attempting to connect to a Server that doesn't exist. for example.