Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to clone repository with submodule url git@github.com: #397

Closed
karthikkolli opened this issue Oct 20, 2021 · 6 comments · Fixed by argoproj-labs/go-git#1 · May be fixed by #464
Closed

Unable to clone repository with submodule url git@github.com: #397

karthikkolli opened this issue Oct 20, 2021 · 6 comments · Fixed by argoproj-labs/go-git#1 · May be fixed by #464

Comments

@karthikkolli
Copy link

When using git:// as a submodule path, the clone fails. Current implementation assumes that submodule paths can either be a http url or relative url.
Source: https://github.com/go-git/go-git/blob/master/submodule.go#L136

Tested sample
error: parse "git@github.com:karthikkolli/subtest_module.git": first path segment in URL cannot contain colon

r, err := git.PlainClone("/tmp/subtest", false, &git.CloneOptions{
  URL:               "https://github.com/karthikkolli/subtest",
  RecurseSubmodules: git.DefaultSubmoduleRecursionDepth,
  Auth:              auth,
})
@terrytangyuan
Copy link

This has been causing a lot of issues for our users. Please consider prioritizing the fix. @mcuadros @smola

@rohankmr414
Copy link

@mcuadros This issue has been fixed on our fork of go-git in https://github.com/argoproj-labs/go-git and we're planning to switch back to upstream go-git, is there any update on this issue?

@rohankmr414
Copy link

cc: @pjbgf

@pjbgf
Copy link
Member

pjbgf commented May 29, 2023

@rohankmr414 I am waiting for #756 to be squashed, which should fix this issue. Would you be able to confirm whether those changes resolve the issues you are experiencing as well?

@rohankmr414
Copy link

rohankmr414 commented May 29, 2023

@pjbgf I believe #464 should fix it, we have it merged on our fork.

cc: @Hunter-Thompson

@pjbgf
Copy link
Member

pjbgf commented Jun 5, 2023

This should now be fixed as per the merge of #756.

@pjbgf pjbgf closed this as completed Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants