GitHub Actions test_pages_build.yaml workflow fails on cross-fork PRs

[eecavanna]

Recent runs (as shown on https://github.com/microbiomedata/nmdc-schema/actions/workflows/test_pages_build.yaml):

Error info:

HTTP 403 stands for "Forbidden":

The HTTP 403 Forbidden client error response status code indicates that the server understood the request but refused to process it. This status is similar to 401, except that for 403 Forbidden responses, authenticating or re-authenticating makes no difference. The request failure is tied to application logic, such as insufficient permissions to a resource or action.

[eecavanna]

In the screenshot above, all the failing runs involve a branch from berkeley-schema-fy24 (i.e. the fork repo) being merged into the upstream repo. I wonder whether the GHA workflow does not handle that.

[eecavanna]

Related: rossjrw/pr-preview-action#6 (credits: I think it was our teammate, PK, that found that related issue)

After having skimmed that issue, I think this is a "known limitation" of the pr-preview-action.

I propose we accept it as a limitation for inter-fork PRs and move on; rather than invest time in fixing it.

With that in mind, I propose this as the task for this ticket:

• Document this limitation and advertise it to contributors so they are not surprised and distracted when this particular GHA workflow fails in inter-fork PRs they create