Skip to content

Potential fix for code scanning alert no. 6: Workflow does not contain permissions #272

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.

Sign up for GitHub

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
majorsilence merged 1 commit into from
Mar 19, 2026
+3 −0
Merged

Potential fix for code scanning alert no. 6: Workflow does not contain permissions #272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/workflows/mac.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
name: mac

permissions:
contents: read

Comment on lines +3 to +5
Copy link

Copilot AI Mar 19, 2026

Choose a reason for hiding this comment

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

Setting workflow-level permissions to only contents: read is likely too restrictive for dorny/test-reporter@v2. That action typically creates/updates GitHub Check Runs to publish test results/annotations, which requires checks: write (and sometimes pull-requests: write for PR annotations). With the current permissions, the "Test Report" step may fail and break the CI job. Consider explicitly adding the minimal additional scopes needed for the reporter (e.g., checks: write), or moving permissions to job-level and granting extra permissions only to the job that needs them.

Copilot uses AI. Check for mistakes.
on:
push:
branches: [master]
Expand Down
Loading