Potential fix for code scanning alert no. 1: Workflow does not contain permissions #2
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/sumithemmadi/json-to-plain-text/security/code-scanning/1
To fix the issue, explicitly set the
permissionskey to limit the permission scope granted to theGITHUB_TOKENduring the workflow execution. The most reliable way to do this is to add apermissions:block withcontents: readeither at the top of the workflow (preferably, so all jobs inherit it), or inside thetestjob definition if you want to limit scope to just this job. Given the provided snippet only contains atestjob and no special needs, it is best practice to add thepermissions:block right under the workflowname:at the top level, ensuring that all current and future jobs inherit this restriction by default. No additional imports, methods, or definitions are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.