Conversation
| TBD, but create the html with `bundle exec jekyll build` then check the content into `asf-site` branch No newline at end of file | ||
| This is currently a manual process. Basic steps are: | ||
|
|
||
| #### Check out `main` and build site |
There was a problem hiding this comment.
We have had success using the https://github.com/peaceiris/actions-gh-pages action to automate publishing static content into another branch for our docs. It's built for GitHub Pages, but setting publish_branch to asf_site and publish_dir to _site might be enough to make it work for this. Here's our workflow if you want to take a look.
There was a problem hiding this comment.
Thank you @phillipleblanc -- the arrow blog has an automated workflow too which I think we could take a friendly look at as well.
I will file a ticket to track the idea
| git checkout -b publish_blog | ||
| # copy content built from _site directory | ||
| cp -R ../datafusion-site/_site/* . | ||
| git commit -a -m 'Publish blog content' |
There was a problem hiding this comment.
if we do a commit should it be followed by push?
There was a problem hiding this comment.
Yes, good call -- will fix
Implement fix found by @comphead in #11 (comment)
Implement fix found by @comphead in #11 (comment)
4 participants
As part of #6 I had to figure this out, so I wanted to write it down
Eventually it would be nice to automate this process but for now at least we can have it documented