-
Notifications
You must be signed in to change notification settings - Fork 109
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
Publishing to github #8
Comments
Having the same issue, and this worked for me. Thanks for the work on this project! 🎉 |
@kalinchernev or @rodrigojv , Any further help is appreciated as I am running into similar problems with the deployment process as well. |
The reason you can use Then you can have a script like this, it's just a combination of other scripts for super-lazy people like me. |
In my case I needed to use |
For someone has same issue to deploy on gh-pages. Following steps are work for me.
|
fwiw - the defaults all worked for me (I didn't have to make any of the modifications described in the comments above) but I did have to manually create a gh-pages branch first. Before that the Travis build was failing when it attempted to clone that "gh-pages" branch that didn't yet exist. |
Thanks @RomanGotsiy ! The above worked for me, adding a new branch called "gh-pages" |
This is out of scope now. |
Hi,
First of all - thank you for making this project - it saved a lot of efforts and time for me!
I have a question about the part of publishing assets to github pages - is there is a specific reason the workflow goes around so many steps?
I personally had some issues with the automatic deployment via travis and simplified this as following:
"gh-pages": "gh-pages -d dist"
, dist === web_deployThis way, the user has the possibility to deploy manually, without setting a token or forcing a https remote variant.
I'm just sharing some thoughts that might be simpler to implement this part, but if there's a specific reason to have the feature in other way, please close the issue directly :)
Again thanks for your work on this project!
The text was updated successfully, but these errors were encountered: