-
Notifications
You must be signed in to change notification settings - Fork 4
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
gh-pages automatically generated on every master push #6
Comments
Necessit PR #4 to be merged to make the linking work |
Not necessary a good idea because gh-pages is the way to expose your project and will be the way for people to use it. So if for any reason it's not stable, you will loose some people. |
The idea here was just to automatize the generation of the gh-pages. If you don't like to generate it from master we can then generate on tags I honestly don't really care and see any difference. That said we need to find a way to control the display yes with kind of integration tests. Too bad you disagree because gh-pages was an easy way to achieve it... Maybe we can deploy several stuff in gh-pages... |
Yeah it's possible with subfolders, we can have :
It is possible using what is described in this gist https://gist.github.com/cobyism/4730490 |
We can even use single-spa framework to have every example in the same webpage (angular + react + vanilla) it is possible. |
The idea to automatize is interesting. I would prefere to do it through a tag |
Roughly, the idea is to add a job/pipeline in circle ci with this command flow :
So that the gh-pages would contains the latest code of monaco-promql. Not necessarily the released one but the master one.
The text was updated successfully, but these errors were encountered: