Skip to content

fix: correct permissions for browsertesting-open-issue workflow #62874

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

Merged
merged 1 commit into from
Jul 23, 2025

Conversation

DeagleGross
Copy link
Member

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:

Run gh issue create
gh issue create
--title "Request Browser-Testing Dependencies Update"
--body-file ".github/workflows/browsertesting-issue-body.md"
--assignee "@copilot"
shell: /usr/bin/bash -e {0}
env:
GH_TOKEN: ***
GH_REPO: dotnet/aspnetcore
GraphQL: Resource not accessible by integration (createIssue)

@Copilot Copilot AI review requested due to automatic review settings July 23, 2025 09:37
@DeagleGross DeagleGross requested review from wtgodbe and a team as code owners July 23, 2025 09:37
@DeagleGross DeagleGross self-assigned this Jul 23, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 permissions block to the create-issue job
  • Grants contents: read and issues: write permissions to enable issue creation

@github-actions github-actions bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Jul 23, 2025
Copy link
Member

@sebastienros sebastienros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other workflows have it so I don't think it's a problem

@DeagleGross DeagleGross merged commit dc3c624 into main Jul 23, 2025
10 checks passed
@DeagleGross DeagleGross deleted the dmkorolev/fix-workflow-browser branch July 23, 2025 09:45
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-preview7 milestone Jul 23, 2025
@wtgodbe wtgodbe modified the milestones: 10.0-preview7, 10.0-rc1 Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants