At the time the deployment failed on forks because we don't provision credentials -- pull_request_target is risky.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.54%. Comparing base (b749e49) to head (80ef4a1).
⚠️ Report is 405 commits behind head on main.

@agoose77 Okay, that makes sense.

We could consider looking for alternatives. For example, we could use Netlify for live previews and GH pages for the "real" documentation. And that way we could ditch AWS.

Netlify has a free tier that seems good. But I'll look at other alternatives.

EDIT: Cloudflare pages looks pretty good. I'll look into that.

I couldn't get it to work with Cloudflare since they don't have doxygen avaliable. I think Netlify could work, but I don't know if the free plan would be limiting.

So I guess let's stick with AWS. I think we can get this to work with workflow_run. We would just need to move the deploy preview job to a workflow with that trigger, and then it can be triggered from the usual docs workflow. It only runs the workflow present on the default branch and has access to secrets, so it gets around the need to use pull_request_target.

The documentation preview is ready to be viewed at http://preview.awkward-array.org.s3-website.us-east-1.amazonaws.com/PR3625

@ianna can you remove "Deploy Branch Preview" from the required checks? Since that is now in a separate workflow it won't show up here.