You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens because the pipeline doesn't have the right to publish the report for the tests.
Option 1: Go in project's settings > Workflow Permissions section and give actions Read and Write permissions.
Option 2: explicitly add the required permissions to the job using this action, e.g.:
Identify all example snippets in our docs that would benefit from the permissions. Can be done by searching for "game-ci/unity-test-runner" in the code (yaml snippets).
Update the examples with the permissions check
Document the error, the fix and the permission check somewhere.
The last thing I would like to validate: if we have the permissions checks in the yaml, I suppose we still have to give actions Read and Write permissions, is that right?
The text was updated successfully, but these errors were encountered:
A note on this: If permissions: is added, all default permissions for other actions in the job are reset and will have to be explicitly added back. As mentioned in actions/checkout#254, actions/checkout will stop working since it needs contents: read permissions, for instance.
Related issue: game-ci/unity-test-runner#249
This message is related to the following StackOverflow:
https://stackoverflow.com/questions/70435286/resource-not-accessible-by-integration-on-github-post-repos-owner-repo-ac
This happens because the pipeline doesn't have the right to publish the report for the tests.
Option 1: Go in project's settings > Workflow Permissions section and give actions Read and Write permissions.
Option 2: explicitly add the required permissions to the job using this action, e.g.:
source: game-ci/unity-test-runner#249 (comment)
permissions
. Can be done by searching for "game-ci/unity-test-runner" in the code (yaml snippets).The last thing I would like to validate: if we have the
permissions
checks in the yaml, I suppose we still have to give actions Read and Write permissions, is that right?The text was updated successfully, but these errors were encountered: