chore(tests): Restrict repository permissions for the test workflow #48
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/ddev/github-action-setup-ddev/security/code-scanning/2
To fix the problem, explicitly set the minimal required
permissionsfor the workflow. Since the workflow does not perform any actions that require write permissions (e.g., it does not comment on PRs, update statuses, or push commits), settingpermissions: contents: readat the workflow level (the root) is the preferred solution. This restricts theGITHUB_TOKENto read-only access to repository contents, greatly reducing the attack surface.Specifically, add the following at the top level of
.github/workflows/main.yml, after thename:and before theon:block:No changes are required to the existing jobs or steps, as none are observed to require greater permissions.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.