Github workflow: PHP backport changes action doesn't work in case of forked repository

[t-hamano]

Description

My understanding is that if a PR contains a file contained in a particular directory, or a PHP file, GitHub Actions will be triggered and a comment will be added to prompt a backport to core. However, this GitHub Actions doesn't seem to work correctly when the PR is sent from a forked repository.

Below is examples:

• https://github.com/WordPress/gutenberg/actions/runs/8081521297/job/22080290754?pr=59438
• https://github.com/WordPress/gutenberg/actions/runs/8067112327/job/22036755769?pr=59410
• https://github.com/WordPress/gutenberg/actions/runs/8081521297/job/22080290754?pr=59438
• https://github.com/WordPress/gutenberg/actions/runs/8060286873/job/22053430171?pr=43451

It seems that creating comments is failing.

Another strange thing is that there was a PR where this GitHub Action was executed even though no changes were made to the PHP file:

https://github.com/WordPress/gutenberg/actions/runs/8057484383

Step-by-step reproduction instructions

N/A

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[t-hamano]

Update: This GitHub workflow is realized by peter-evans/create-or-update-comment. If I look at the README, it mentions the following, so this may be related.

Note: In public repositories this action does not work in pull_request workflows when triggered by forks. Any attempt will be met with the error, Resource not accessible by integration. This is due to token restrictions put in place by GitHub Actions. Private repositories can be configured to enable workflows from forks to run without restriction. See here for further explanation. Alternatively, use the pull_request_target event to comment on pull requests.

[t-hamano]

This workflow has been removed as of #62609 and should no longer cause the issue.