-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action fails with "HttpError: Resource not accessible by integration" (v1.3) #24
Comments
This problem is related to dependabot instead of the action's version. |
It is possible to change the action's token read/write permissions to the needed permission but I dont know which permission is required. |
Ran into this because my workflow had custom permission defined (and per docs, any unspecified permissions default to |
@suniastar |
I know about that but I dont have that option in my settings. The "complete" list of default permissions for the token is listed here: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token But this list does not include the default permissions for dependebot. I have tested all important access rights on one of my repositories.
When any github workflow is initiated by dependebot (e.g when it creates a PR because of a new version) the token's permssion will be set to In my option simply adding: permissions:
pull-requests: write to the workflow file should be enough (as @cengdall said) but I did not test if |
At least in my repository, i needed the contents-read permission as well: permissions:
contents: read
pull-requests: write Otherwise I got a "Repository not found" error during the checkout action:
|
Thanks @suniastar for investigating this. I already have a PR #26 to add this |
When using the github action with this workflow
the workflow fails with:
however when using the main (
Madrapps/jacoco-report@main
) branch the worklfow completes successfully without a problem.This does not make sense to me as the commits since the latest version (v1.3) only consists of
README
updates.Does anyone has an idea what could cause this problem?
The text was updated successfully, but these errors were encountered: