chore: Publish docs#166
Conversation
raulcd
left a comment
There was a problem hiding this comment.
@kou are those scripts and workflows based on any other of our repos or is this process completely different? I am currently losing track on how we do things on others. I tried to understand what was going on with the different branches / directories / forks and really got it when I read the description of the PR. It seems quite important to understand the process, should we add something similar to the PR description to the documentation?
In general looks good to me, I am just slightly concerned whether we will be able to remember what was going on with the different branches/folders/workflows once we have to update it in the future.
These implementations are completely different from others. apache/arrow-adbc and apache/arrow-nanoarrow are only automate documentation publishing. apache/arrow-adbc nor apache/arrow-nanoarrow don't support preview by GitHub Pages on fork. So apache/arrow-js implementation is (a bit?) more complex than them.
Good point. I'll add |
Thanks, I think this will be helpful in the future. |
Co-authored-by: Raúl Cumplido <[email protected]>
|
|
What's Changed
Build docs by CI and:
Push an RC tag:
Push a release tag:
https://arrow.apache.org/js/{current,${VERSION}}via the asf-site branchPush to main in apache/arrow-js:
Push to non main in apache/arrow-js:
Push to foks:
Closes #10.