Potential fix for code scanning alert no. 6: Workflow does not contain permissions #52
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/DevCycleHQ/feature-flag-code-usage-action/security/code-scanning/6
To fix the problem, add a
permissionsblock to restrict the GITHUB_TOKEN access to only the necessary scopes for this job. The most secure starting point is to setcontents: read, and then expand with additional permissions as needed (for example,issues: writeorpull-requests: writeif the workflow creates or updates issues/pull requests). In this snippet, we cannot see any evidence that write access is needed (no calls to push, PR, or issue creation), socontents: readsuffices as a minimal default. Place thepermissionsblock either at the workflow root (applies to all jobs) or within thedvc-code-usagesjob itself (applies only to this job). For simplicity and minimal change, add it at the root, immediately followingname:on line 4.No new methods or imports are needed.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.