kou commented on PR #166:
URL: https://github.com/apache/arrow-js/pull/166#issuecomment-2987112576
> are those scripts and workflows based on any other of our repos or is this
process completely different?
These implementations are completely different from others.
Documentation URL style (`/js/{main,current,${version}/') is same as ADBC's
one.
apache/arrow-adbc and apache/arrow-nanoarrow are only automate documentation
publishing.
(apache/arrow also automates dev documentation publishing but apache/arrow
uses separated apache/arrow-site repo. So it's not done in each commit of main
in apache/arrow.)
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.
> 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?
Good point. I'll add `dev/release/docs.md`. I don't want to add it to
`dev/release/README.md`. I want to keep `dev/release/README.md` just about our
release process.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
