ci: potential fix for code scanning alert #103
Merged
+3
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
nicklasl
changed the title
fabriziodemaria
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/spotify/confidence-resolver-rust/security/code-scanning/1
To fix this problem, an explicit
permissionsblock should be added in the workflow file. This block limits the scope of theGITHUB_TOKENto the minimal permissions necessary for the workflow to work—specifically, the ability to read repository contents and write to pull requests (leave comments). The best place to add this is at the root level of the YAML file, just below the workflownamefield (and aboveon:), so the permissions apply to all jobs in the workflow unless overridden at the job level. This is a non-disruptive change and does not affect any functional logic in the workflow—just the security context it operates under.Suggested fixes powered by Copilot Autofix. Review carefully before merging.