-
Notifications
You must be signed in to change notification settings - Fork 279
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
Cannot clone a bundle from an SSH repo with custom port #490
Comments
Same issue here |
I'm gonna look for a fix! Thank's for reporting! |
Can you have a look at #491 too for 2.0.1 milestone. Actually this issue resulted from the other one - instead of loading a bundle from a local filesystem I tried to load the bundle from Gitlab. |
Work in progress here if you can take a look at it. |
@mgryszko btw you may try
as a workaround. |
Available in |
That was fast, thanks! Will give it a try
El jue., 13 abr. 2017 20:01, desyncr <notifications@github.com> escribió:
… Available in develop. Ready for 2.0.1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#490 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AByHBE2Vz9f0E0NfrLZ-RJJjUUGC9lzAks5rvmMKgaJpZM4M7GR4>
.
|
Confirmed, working as expected |
When trying to add a bundle in Antigen 2.0.0 with SSH Git protocol and custom port:
followed by
antigen reset
, I get this error in the log:The Git repository is an internal company repository managed by Gitlab. I removed the URL and the actual repo name due to confidentiality issues.
This was working in 1.4.1 so it's a regression bug for me.
The text was updated successfully, but these errors were encountered: