Skip to content

Potential fix for code scanning alert no. 248: Workflow does not contain permissions #242

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
projectedanx merged 1 commit into from
Jul 6, 2026
Merged

Potential fix for code scanning alert no. 248: Workflow does not contain permissions #242

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
4 changes: 4 additions & 0 deletions .github/workflows/defender-for-devops.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ on:
schedule:
- cron: '32 9 * * 4'

permissions:
contents: read
security-events: write
Comment on lines +29 to +31

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Add actions read for private SARIF uploads

If this workflow runs in a private or internal repository, this explicit permissions block now sets every omitted scope to none, so the later github/codeql-action/upload-sarif@v4 step loses actions: read. GitHub's SARIF upload example marks actions: read as required for private-repository workflows, and the other SARIF-upload workflows in this repo grant it for that reason; without it the upload can fail even though security-events: write is present.

Useful? React with 👍 / 👎.


jobs:
MSDO:
# currently only windows latest is supported
Expand Down
Loading