fix: correct permissions for browsertesting-open-issue workflow - #62874
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a permissions issue in the browsertesting-open-issue GitHub workflow by adding explicit job-level permissions. The workflow was previously failing with a "Resource not accessible by integration" error when attempting to create GitHub issues because the default GITHUB_TOKEN lacked sufficient permissions.
- Adds explicit
permissionsblock to thecreate-issuejob - Grants
contents: readandissues: writepermissions to enable issue creation
sebastienros
approved these changes
Jul 23, 2025
sebastienros
left a comment
Member
There was a problem hiding this comment.
Other workflows have it so I don't think it's a problem
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
continuation for #62845, it appears that we need to set permissions on the job so that GH_TOKEN has enough rights to open the issue. see failed workflow run: https://github.com/dotnet/aspnetcore/actions/runs/16465776673/job/46542680254 and error: