-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
clone from private repository #525
Comments
From readme:
|
@posva thanks for quick prompt
or it's just the bug of my |
I see the bug, I'll fix it |
I gave it a look but I don't understand why the order is being messed up when loading the args. Can you take a quick look @egoist , please? |
BTW, using the option at the end works as expected |
Not sure if this helps, but this appears to work (just replace
|
Im having a similar kind of issue with the custom template and its hosted in my work's private bitbucket repo and get the following error:
I tried all the mentioned steps: When I put in on a public Github repo it works fine but not sure why its not working with the private bitbucket repo? When I do git clone bitbucket of the exact repo it works fine as so I can tell its not the connection issue with SSH.
Any help would be highly appreciated. Thanks. |
@bajras did you try replacing |
@mrcsmcln yes, that didnt work either. |
me too, In Window OS. I pull a request fix the bug.
|
commander appears to be switching the order of the args. vue init a b Program.args[0] === a vue init -c a b Program.args[0] === b Perhaps an iterating through an object with no guarantee of order. |
Running vue init --clone a b Causes Commander.prototype.parse to be run twice. First for 'vue' which results in '--clone a' being seen as an unknown parameter. The unknown parameters are then tacked back on in Commander.prototype.parseArgs. Personally, I'd see this as a bug in Commander which could do better with named arguments. That said --clone is not a named argument, it is being used as a switch and Commander does not seem to support argumentless switches. It is perhaps less confusing to suggest users use the following command vue init --clone=true a b |
I pull a request fix the bug # There will be errors in the windows
vue init gitlab:http://192.168.1.125:nodejser/templates my-project |
@bajras Did u manage to solve this? Installing templates from your works private repo? |
Has this been fixed on OSX? I see that it was closed on Aug 18th, and reopened for window's OS. Unfortunately I can't get this to work either. I've tried all options mentioned in this thread. |
I have not been able to get it work. Had to clone the repo first locally and then do the |
@bajras I got the same problem! After format the git repo url, it works. Vue-init get template from remote repo with download-git-repo which check your url format. So, just run: |
Same error: |
i use private gitlab, the vue-cli version is
2.8.2
if i clone with project-name like this
it show err:
it seems that the order of argument is wrong
use this cammnd is work fine
and this
The text was updated successfully, but these errors were encountered: