Honestly I would be in favour of moving back the doc builds to CircleCI. This would simplify the setup quite a bit ... is there a good reason not to do this?

This would look (like in the goold old days 😉):

• build doc and upload browsable artifacts on CircleCI

The way it looks right now:

• build doc on github actions and upload artifact
• kick CircleCI build with curl from github action (needs an noop build on CircleCI for this)
• Circle CI downloads artifacts from GHA and uploads its to its artifact which can be browsed

Alternative option since we are not using CircleCI for linux-arm64 now would be to use Netlify to have browsable artifacts, see https://github.com/INRIA/scikit-learn-mooc/blob/main/.github/workflows/jupyter-book-pr-preview.yml where I did that for the MOOC.

There are some limitation on Netlify but we can ask for an open-source plan if we think we need it.

Honestly I would be in favour of moving back the doc builds to CircleCI. This would simplify the setup quite a bit ... is there a good reason not to do this?

I think so. I trust you regarding taking decisions to adapt this setup for the best (i.e. probably the simplest).

@lesteve I am okay with moving back to CircleCI. You are welcome to ping me on a PR that makes that move.

I had a sketch of a way to host PR docs without CircleCI using GitHub pages (on a separate repo), that should be secure. But I did not want to invest time in it, because GitHub plans to do it in the future: community/community#7730 (comment).