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
Review Github Action permissions, allowing it to create issues.
Purpose
We're setting up automation that creates new issues when tests fail on the main branch (open-telemetry/opentelemetry-collector-contrib#38270), and when calling the GitHub API we're failing with the error below:
Failed to create GitHub Issue {"error": "POST https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib/issues: 403 Resource not accessible by integration []"}
To be transparent, I'm not 100% sure if this is a repository settings problem or something else, but I'm running out of ideas 😅.
hi @ArthurSens! the default GITHUB_TOKEN doesn't have write permission when github actions are run from PRs (but it does when the github action is run from main)
Hmmmm, I see... that explain things. @mx-psi should we try it together at KubeCon if you have free time? I can clean up that PR and we coordinate the merge to test
Hmmmm, I see... that explain things. @mx-psi should we try it together at KubeCon if you have free time? I can clean up that PR and we coordinate the merge to test
Affected Repository
https://github.com/open-telemetry/opentelemetry-collector-contrib
Requested changes
Review Github Action permissions, allowing it to create issues.
Purpose
We're setting up automation that creates new issues when tests fail on the
main
branch (open-telemetry/opentelemetry-collector-contrib#38270), and when calling the GitHub API we're failing with the error below:To be transparent, I'm not 100% sure if this is a repository settings problem or something else, but I'm running out of ideas 😅.
The idea is based on this discussion: https://github.com/orgs/community/discussions/60820#discussioncomment-6445895
Expected Duration
Permanently if this is indeed what was missing to make the workflow work. If it's not, we can revert the new permissions.
Repository Maintainers
The text was updated successfully, but these errors were encountered: