Preview of documentation

[devmotion]

No description provided.

[devmotion]

Ah this needs more changes, the custom DeployConfig overwrites the pull_request event and so Documenter does not create a preview build but instead rebuilds the actual docs since it assumes we pushed to master.

It seems one should also not build both stable and dev in a PR. In general, maybe there should be separate triggers for the stable builds only if there is a new release of Turing - it seems a bit strange to rebuild it every time the action is executed.

[devmotion]

Maybe one should first separate the repo more clearly from Turing, as discussed in TuringLang/Turing.jl#1474.

[cpfiffer]

Ah this needs more changes, the custom DeployConfig overwrites the pull_request event and so Documenter does not create a preview build but instead rebuilds the actual docs since it assumes we pushed to master.

We should probably just check an environment variable here -- the deploy config I added was to allow this to function more like a cron job, but maybe there's a better way to do it.

It seems one should also not build both stable and dev in a PR. In general, maybe there should be separate triggers for the stable builds only if there is a new release of Turing - it seems a bit strange to rebuild it every time the action is executed.

This was a quick hack to get it to remain current. I wasn't able to find a way to have GitHub report pulls/releases in other repos to this one, and this is a nice and easy stateless solution that doesn't require talking to the main Turing.jl repo or performing any record keeping.

[cpfiffer]

Maybe one should first separate the repo more clearly from Turing, as discussed in TuringLang/Turing.jl#1474.

I'm also not sure what you mean here -- everything that's in this repo is basically just website skeleton. The whole point of make.jl is to go grab any of Turing docs and build them in the website format. It's very separate from Turing.

[devmotion]

I'm also not sure what you mean here -- everything that's in this repo is basically just website skeleton. The whole point of make.jl is to go grab any of Turing docs and build them in the website format. It's very separate from Turing.

I got confused by the setup and only realized this later. Just ignore this comment 🙂

[devmotion]

This is not useful, as mentioned above it just rebuilds the stable and dev version of the docs. However, the main motivation would be to build it in a separate folder for each PR.