-
-
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
Allow vue-create Presets to Target Github Enterprise #3384
Comments
We are aware of and are using the workaround of having the generator repo pulled down locally, but this means that the user will need to manage their local repo in order to use the generator. By adding a way to set up the domain to use Github Enterprise, we can ensure developers are consistently using the same, most up-to-date version of the generator. |
+1 |
I think it's already supported. Since this feature is built on top of
|
So far, that command has not worked for me. I'm not using Gitlab. I am using Github enterprise. Using the direct ssh method does not appear to work. I get |
Is the |
Yes. The clone flag is correctly added. This feature does not work. |
Can this ticket be re-opened since it wasn't actually fixed and was closed before any confirmation was made over whether it was fixed? |
You should rather report it to download-git-repo, though. |
And I personally don't have access to a GitHub enterprise server, so there's much I can help you with. |
for whom it may concern: as a workaround, i created a dedicated CLI tool to ease the process of cloning templates/presets hosted on enterprise/private repositories and storing them locally. |
What problem does this feature solve?
My company uses github enterprise so the preset we want to target is not located on github.com, gitlab.com, or bitbucket.com.
I would like to be able to run the command
vue create --preset <url to my company's private github instance>
or some other mechanism to indicate the domain.What does the proposed API look like?
vue create -preset <domain>/repo_name
The text was updated successfully, but these errors were encountered: