Potential fix for code scanning alert no. 59: Workflow does not contain permissions #1223
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.
Potential fix for https://github.com/flatcar/nebraska/security/code-scanning/59
To resolve the problem, add an explicit
permissionsblock to restrict the permissions granted to the GITHUB_TOKEN during workflow execution. The best practice is to assign the least privileges necessary. For workflows that only need to check out code and build/test, settingcontents: readat the workflow root or job level is sufficient.Since there is only one job, it's most effective to add
permissions: contents: readat the root level (directly aftername:or afteron:), which will apply to all jobs by default.Edit needed:
.github/workflows/backend.yml, addnameand before theonblock (line 2).No other imports, methods, or definitions are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.