Closed SirMishaa closed 1 year ago
Interested as well, as it started failing for us as of today.
Weird that this just started happening for you.
It sounds like a permissions issue or perhaps a GitHub service issue. From what I've read, the GITHUB_TOKEN contains default permissions which can be found here: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token. Now it also mentions, "People with admin permissions to an enterprise, organization, or repository, can set the default permissions to be either permissive or restricted.". I'd first check that this isn't the case for your organization's configuration.
If that doesn't work, then try overriding permissions within the workflow file.
jobs:
testing:
permissions: write-all
steps:
....
- uses: joshmfrankel/simplecov-check-action@main
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
Permissions documentation can be found here.
If that doesn't work then try switching ${{ secrets.GITHUB_TOKEN }}
to utilize a personal access token. More details here: https://stackoverflow.com/questions/70435286/resource-not-accessible-by-integration-on-github-post-repos-owner-repo-ac/70448851#70448851
I'm going to go ahead and close this issue for now. Let me know if the directions above fail to solve the issue
I was facing this issue. I solved it by going to repository settings > Actions > General > Workflow permissions and setting Read and Write permissions.
Hello, at work, I got this issue :
We're running on an organization, in team plan We're using the following in our workflow:
Do you know what happens?