chore: Add explicit permissions for ldotel ci #278
Merged
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/launchdarkly/go-server-sdk/security/code-scanning/16
To fix the issue, we need to add a
permissions
block to the workflow. This block should specify the least privileges required for the workflow to function correctly. Since the workflow performs basic CI tasks (unit tests, linting, and coverage checks), it likely only requirescontents: read
permissions.The
permissions
block can be added at the root level of the workflow to apply to all jobs, or it can be added to individual jobs if different jobs require different permissions. In this case, adding it at the root level is sufficient and simplifies the configuration.Suggested fixes powered by Copilot Autofix. Review carefully before merging.