-
-
Notifications
You must be signed in to change notification settings - Fork 14
Distributed Execution #1260
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
base: main
Are you sure you want to change the base?
Distributed Execution #1260
Changes from all commits
ad70084
739a34d
b44a055
d510d00
22b1153
e69e076
d2b7a1d
0bf1acc
f3d7b20
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Copilot Autofix
AI 7 days ago
To fix the problem, add an explicit
permissions
key at the top level of the workflow file (.github/workflows/dotnet.yml
) so that all jobs get minimal privileges unless overridden. The vast majority of .NET build/test/package steps do not require write permissions to the repository;contents: read
is usually sufficient. If any job specifically requires additional permissions (e.g., to make PR comments or create releases), that job should get a specificpermissions
override, but that is not evident in the provided snippet.Steps:
permissions:
block right after the workflowname:
and beforeon:
(best practice and visually separates configuration sections).contents: read
as the explicit minimal starting permission, following CodeQL’s recommendation.