Potential fix for code scanning alert no. 4: Workflow does not contain permissions #332
+2
−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> Signed-off-by: Kurt Garloff <[email protected]>
garloff
added
bug
mbuechse
approved these changes
Dec 3, 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/SovereignCloudStack/docs/security/code-scanning/4
To address the detected issue, we should explicitly add a
permissionsblock to the workflow or the affected job. Because the "Deploy" step requires the workflow to push built assets to thegh-pagesbranch, it needscontents: write. All other operations should only need read permissions. To minimize the scope while allowing required functionality, add apermissionsblock to thebuild_and_deployjob:Place it directly under the job name (
build_and_deploy:), beforeruns-on. No new dependencies, methods, or imports are required. This change ensures the GITHUB_TOKEN provided to the job is restricted to justcontents: writeand nothing broader.Suggested fixes powered by Copilot Autofix. Review carefully before merging.