Potential fix for code scanning alert no. 1: Workflow does not contain permissions#410
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#410
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Kurt Garloff <kurt@garloff.de>
fkr
approved these changes
Dec 8, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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/calendar/security/code-scanning/1
To fix this problem, you should declare a
permissionsblock to restrict the permissions of the GITHUB_TOKEN issued for this workflow/job to only what is necessary. Since the workflow deploys withactions-gh-pages, it needs permission to write to repository contents, socontents: writeis required. Place this block either at the top level of the workflow or inside the specific job that does the deploy. For this workflow, adding it at the job level (to thedefaultjob under line 9) is preferred for clarity, but adding it at the top level achieves the same effect for a single-job workflow. In this case, update.github/workflows/yaml2ics.ymlto insert:at the appropriate location. No imports, definitions, or other code changes are needed.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.