Cannot clone GitHub repository due to corporate proxy

[MyResearchExchange]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Cannot clone a GitHub repository due to corporate proxy settings.

Steps to Reproduce

1. Ctrl + P
2. GitHub: Clone

Expected behavior:

Clone a GitHub repository

Actual behavior:

Unsupported proxy syntax in '...'

Reproduces how often:

• The error occurs every time. Even if not behind a proxy, e.g., at home.
• Changes in the .apmrc-file take no effect.
• Everything else in atom works, like downloading packages for example.

Versions

Atom : 1.50.0
Electron: 5.0.13
Chrome : 73.0.3683.121
Node : 12.0.0

apm 2.5.0
npm 6.14.5
node 10.20.1 x64
atom 1.50.0
python
git
visual studio

[sadick254]

I can't reproduce this on macOS Catalina 10.15.6. Which operating system are you using?

[MyResearchExchange]

I am using Windows 10 (Version 1809).

[MyResearchExchange]

Just found a quick and dirty solution for my problem:

1. I changed my gitconfig file under C:\Users\<username>\AppData\Local\atom\app-1.50.0\resources\app.asar.unpacked\node_modules\dugite\git\etc

2. I removed the lines

[http]
	sslBackend = schannel
	schannelUseSSLCAInfo = false

3. I added the lines

[http]
	proxy = http://<username>:<password>@<address>:<port>
[https]
	proxy = http://<username>:<password>@<address>:<port>

I don't know what's the actual bug in the code and it does not solve the actual problem, but I am able to work with git at least. Maybe it helps to fix the bug in a future version...

[smashwilson]

The git client we use internally should pick up settings you make in your usual ~/.gitconfig.

Does it work if you set those git config settings normally, without editing the system config in dugite?

git config --global http.proxy http://<username>:<password>@<address>:<port>
git config --global https.proxy http://<username>:<password>@<address>:<port>