metanorma/metanorma#202 respect HTTP[S]|SOCKS_PROXY env vars during git clone

[CAMOBAP]

• Implement support for HTTP/HTTPS/SOCKS proxy usage metanorma/metanorma#202

Open questions

• Should we handle a case git repos which were cloned with proxy and then metanorma executed without proxy?

Related PRs:

• metanorma/metanorma#202 add socksify dependency and support SOCKS_PROXY env var metanorma/metanorma-cli#247

[alexeymorozov]

Looks good to me 🔥

[ronaldtse]

Should we handle a case git repos which were cloned with proxy and then metanorma executed without proxy?

For simplicity reasons let’s not support the “per git repo proxy” case. Thanks!!

[CAMOBAP]

For simplicity reasons let’s not support the “per git repo proxy” case. Thanks!!

Great, users still will be able to do clone by providing a proxy in global ~/.gitconfig. I will write about it in blog post

Also, we have two big pros for this approach:

• ruby-git gem doesn't support default_branch API right now, I just hardcoded 'master' but this may not work for all repos, I have prepared PR for ruby-git
• ruby-git don't support depth for git fetch which passed by fontist this also may create some difficulties

Just to make sure that we are on the same page, I'm going to close this without merge, @ronaldtse @alexeymorozov any objections?