The current implementation disregards of the ~/.ssh/config in most cases in favor for default values etc.
When I was trying this out against the company servers I failed to clone projects from the company server since the cloning address assumed the user and port specified in the ssh config file.
I think these changes will solve my little problem however I'm having great difficulty to use the commit as a package in my other files to try it out.
Would be very happy If anyone would like to try it out/ explain how I should go about using the local project to build my binary so I'm certain that the commit contains the correct behavior.
This is a start regarding: #1220 but I need some more guidance.
The current implementation disregards of the ~/.ssh/config in most cases in favor for default values etc. When I was trying this out against the company servers I failed to clone projects from the company server since the cloning address assumed the user and port specified in the ssh config file.
I think these changes will solve my little problem however I'm having great difficulty to use the commit as a package in my other files to try it out. Would be very happy If anyone would like to try it out/ explain how I should go about using the local project to build my binary so I'm certain that the commit contains the correct behavior.
This is a start regarding: #1220 but I need some more guidance.
closes #1261
Best regards, Signed-off-by: Måns Ansgariusson mattemagikern@gmail.com